Introducing Rollover Downloads. Now get even more from a subscription! Find Out More Close

What is the Perfect Web Design Application?


As designers we spend huge portions of our days staring into screens, looking at the same buttons and dialogs and essentially repeating the same processes over and over again, so hopefully it’s not unjustified to sometimes question the tools of our trade that essentially become our lives when we’re in front of our computers.

Unfortunately, In my opinion the perfect web design application for professionals simply doesn’t exist yet. I’d say that’s a sad thought, that after this long we still don’t a powerful tool designed specifically for what we do. Most professional designers use Photoshop to mock up concepts for designs, some use Fireworks and others Illustrator - there are also open source, and cheap alternatives to these applications such as GIMP, Inkscape, and Pixelmator, the list goes on.

Some people even omit design applications out of the process all together, and although that might be fine if you’re good at CSS prototyping I find it hard to believe you can be as creative with pure CSS as with a design tool in your workflow.

All methods have their good points and bad points but none of them really hit the spot, none of them are that beautiful, intuitive, powerful, and even fun to use tool we could really do with in our workflow. Web designers need something that does for our industry what InDesign did for print when it overtook Quark Xpress and what Coda and Espresso have done for Mac coders (good riddance Dreamweaver)

This is of course a personal opinion post, and some of you may already be thinking Photoshop is the ideal tool, I discussed some of the points that makes Fireworks better for web design than Photoshop in an earlier post. But this time I want to look at the larger picture for a moment, give my arguments for why neither application is the ideal solution and pitch ideas for what the perfect design app could be.

Why Photoshop isn’t the answer

It’s easy to see why Photoshop is the number 1 tool for web design at the moment, and it’s certainly not it’s ease of use and affordability, no the reason is simply it’s popularity. Photoshop is so popular that it has practically become a verb in the English dictionary ie. “To photoshop”.

It’s immense popularity of course means that it’s making tons of cash for Adobe who can then in turn, invest that cash in the app, and develop additional, high-powered features to implement. That’s the way business works and developing the app acts as marketing for Photoshop, so Adobe releases their (almost annual) update to the package and predictably sales boost. Rinse, repeat. It’s a cycle that’s been going on for over 20 years.

Where’s the problem in that? In terms of business strategy nothing, it’s the ideal situation, but it can sometimes feel like Adobe never steps back and thinks okay what do our users actually need in their workflow? I’m pretty sure not many people were saying they needed 3D features in Photoshop before CS5 came out, were they? I think it’s more likely people were having simple requests such as improved reliability and speed.

Despite those reasons though, Photoshop is lacking many features needed for web design - it’s purpose is as a photo editing application not a design tool, things like multiple pages, dynamic styles and libraries of reusable items are somehow absent from Photoshop in favor of marketing features for photographers like Vanishing Point, Content Aware Fill and Puppet Warp,

So, this isn’t a dig at Photoshop exactly, which is an incredibly powerful application, it’s just clearly not an app designed for web design.

Why Fireworks isn’t the answer

Fireworks is the one tool in Adobe’s Creative Suite that is actually marketed as a UI and web design application, it’s my personal preference at the moment but unfortunately as far being a web design application goes it wouldn’t be my first choice if there were alternatives.

It’s interface is old-fashioned and clunky, it’s bitmap editing abilities run a little short of Photoshop’s and although it doesn’t crash nearly as much Photoshop, it still does have it’s fair share of quirky bugs.

It’s also passed hands over the years from Macromedia when Adobe acquired the company, this shows in the user interface and workflow, for example that color picker is a relic from Macromedia’s glory days, is it actually difficult to update the color picker or do Adobe think former Macromedia users will be furious if they touch it?

Why Illustrator isn’t the answer

Pure and simply because it’s a vector-based application, I for one am looking forward to CSS3 popularity and widespread SVG support for a resolution independent web but we can’t just throw away our bitmap editing abilities yet and switching back and forth from Illustrator and Photoshop isn’t really ideal for a seamless workflow.

Illustrator suffers from the same problems as Photoshop, it’s an almost perfect vector drawing application, but it is what it is, it’s not a web design app.

What is the answer?

I believe that the answer is a combination of all the best features in these apps, a unified version of all of the Creative Suite  in a single app if you will, except with all the stuff designers don’t need or care about cut out and then sprinkled with some innovation, and an intuitive workflow.

The way a lot of photographers work was completely changed by the release of Apple Aperture and Adobe Lightroom - it seems odd that both companies released their software at about the same time, I can’t comment on who had the idea first but as a casual photographer myself, it completely did away with using Photoshop for processing my shoots after the release of Aperture, and the way my workflow improved was nothing short of incredible.

It seems so obvious now but for years I didn’t even question the way I worked, I assumed post-processing photos was supposed to take hours of frustration and hair pulling.

So an innovative workflow is a must, it should be created with modern web designers and their workflow in mind, here are some key features that would be refreshing to see to see in a web design app:

The Canvas Should Have Screen Real-Estate Priority

Why can we see gradients, strokes, swatches, color sliders, masks etc. when we aren’t even using those features? and even worse why can we see grayed out windows when something is inactive instead of it hiding itself and showing more of the canvas? the canvas should be our top priority.

Cataloging Features for Reusable Design Resources

Kind of like Adobe Bridge except with better implementation, interface and speed, it would be great to be able to build a library of resources split up into categories, from brushes to stock photos, all easy to access and drop into any design.

Decent Presets

The person who designed the default Adobe patterns, gradients and symbols needs to be shot. Just imagine opening up a design application and finding a plethora of usable styles, basic shapes, icons and buttons.

CSS Functionality

Why not implement a feature that mimics a browser rendering engine, so you can apply a ‘CSS Drop Shadow’ and get the options that are available in CSS, with realistic rendering and maybe an option displaying the exact CSS property for easy copy and paste into projects.

This shouldn’t be confused with WYSIWYG HTML applications like Dreamweaver and Flux, I mean realistic CSS effects within a Photoshop-like environment to help us plan what needs to be images and what can be CSS in the final coded design.

Pages and Interaction

This is something that Fireworks already implements to a certain degree, but is an essential feature to have in a design mockup application, this feature enables you to create multiple pages within a single design file, with master pages etc. and interactive buttons that link to different pages within the design (with hover and active states) so that you can navigate through the site as if it were in a browser, exporting to PDF would be a handy feature too for sharing your concepts with clients in way that enables them to click through it (no more explaining the different between Jpegs and websites).

Adobe Integration

This is a necessity, a new application in the market would need to play nice with Adobe (atleast initially *evil laugh*), export to PSD is the most obvious feature required, but the ability to open files interchangeably between applications and an “Edit in external editor…” would be great for jumping into Photoshop just for certain operations.

Beautiful User Interface

It needs to be pretty to look at because we web designers love judging books by their covers (well, I do anyway) but not just for the initial sale, a pretty, easy to use interface will make our days more pleasant and us more productive.

Slicing and CSS Export That Works

I never use these features personally, they remind me of the Dreamweaver age as it were, with table layouts and image maps but if they are going to be in a application they could at least export code you wouldn’t be ashamed to upload, with up to date standards and a level of intelligence that can spot repeating patterns and dynamic text etc. and generate them correctly.

Lightweight and Stable

This one is self explanatory but nothing is more frustrating in a web designers day than when Photoshop unexpectedly crashes. No matter how recently they saved, it just shouldn’t happen. Also, the less bloat in the app the better, just because hard drives have huge capacities now and SSD memory is super speedy it doesn’t mean an app should be 500MB and need a splash screen to keep you entertained while it starts up.

Conclusion

Today, the best web design tool you can use is the Adobe Creative Suite - whether it be Photoshop, Fireworks, Illustrator or a combination of them all, there’s simply nothing else that comes even close at the moment. However I see this as an open market, of course nobody wants to be competing with the almighty Photoshop, that’s fair enough as it would take years and years of playing catching up. But in actual fact a web design application would be hitting a niche that Photoshop only covers at the moment by default.

I’d love to hear what everybody’s thoughts on this, has anybody else ever thought the same thing? and it’s a long shot but is anyone secretly developing the app described above?

Category: Articles

MediaLoot Treasure Chest Download ALL of Our Premium Resources

Signup for a MediaLoot subscription today and get tons of premium resources to use commercially and even in web apps. At subscriptions starting at just $9, you can't lose...

Learn More or Join Us →

Comments

  • Mar 9, 2011 at 5:18 pm

    Nice article! Liked it very much. I agree on the matter, but the actual problem is bigger than most of us think! It is Adobe’s politics towards their software! If sw sales are big, they put more money to develop new versions, but sw like Fireworks don’t sell as good as PS, that is why its dev so slow! Kinda steped away from the matter, but the point is that Adobe will not give up such power easily, because it brings a shitload of money to the company. And they will never, probably in the near future, UNITE progs like you suggested. Maybe in CS8, but who knows!

  • Mar 9, 2011 at 5:25 pm

    I think you’re absolutely right, I didn’t want to get into Adobe politics too much but what you say is true, I don’t think Adobe are ever going to unite their programs, not with the amount of money people pay for 80% the same features in each of their design apps lol.

    My hope is for a completely new competitor app to the market (ideally not made by Adobe)

  • Mar 9, 2011 at 5:43 pm

    Nice read, keep up the great work and resources!

  • Mar 9, 2011 at 5:56 pm

    Do you think Adobe is THAT stupid to give a chance to some sw to arise above them, because that is why they made Macromedia’s acquisition. They saw the potential of the rival company. Macromedia had in their arsenal Dw, Fw, Director, Freehand, Flash, on the other side was Photoshop with a handful of blending modes, lesser than Fw had that time btw, what else, heeey, ugly GoLive!, imageready… with no potential. the acquisition went well and now Adobe is the largest player there, with their rules towards projects they “don’t” like (FW), maybe I am wrong. Fw is not even listed as their flagman progs in the product list. I don’t know, just a thought…. but the future is not so bright as we wish for.

  • Mar 11, 2011 at 11:56 am

    The problem with going up against Adobe is that everyone trains and learns on the software. So either you copy how the software works or there is a learning curve to get to grips with the new app. This is ok when you are learning your trade but not when you need to turn round the projects in a week. The other issue is that businesses already have creative suite installed so why pay for more software that no-one can use?

  • Mar 11, 2011 at 12:23 pm

    That’s a fair point, but in theory it’s the same as a Windows-based office deciding to switch over to Macs, sure it will be different at first and although both systems both have the same basic purpose there are differences and there will be a learning curve period when productivity may take a hit because nobody knows how to use Macs yet, but if the new systems are more productive to that particular line of business then the switch will soon pay off.

    It’s not something that’s going to be forced upon anyone, and I don’t even think it should be considered as taking on Adobe, it’s more like filling a niche. A professional web design application, made for designers not photographers.

  • Mar 11, 2011 at 3:24 pm

    Yeah I understand what you’re saying I think there is a niche but trying to fill the gap in the market on a scale you would need to have any penetration would take a lot of marketing power.

    The more I think about it, the more I believe it would be adobe that would release the product that your after, rather than a third party releasing a product that would have to fit so nicely inside the creative suite.

    Essentially you are right though we do need our own dedicated application.

  • Mar 17, 2011 at 12:30 pm

    .... Yes, @Html Codes Dude, that is exactly what I intended to say but instead kept circling around the idea. I just want to add something… Eventually Adobe will integrate all these features into one prog, but when it would be no one knows, the reason is that they probably want to squeeze more out of their standalone projects Ps, Ai and others. By joing them they will lose a big amount of pro-users, and that is not good for business… figure out the rest.

  • Keith Chastain
    Mar 19, 2011 at 3:05 pm

    I’ve been thinking for some time that I would love to see Apple go head-on with Adobe in the design software scene. Apple is extremely smart and resourceful and their UX expertise is second to none.

    For Mac users at least, this would be exciting.

  • Apr 3, 2011 at 9:40 pm

    Thanks for this article - it was a good read.

  • May 17, 2011 at 2:49 am

    So… I take it no one has any favorite web design apps then..?  smile

  • Sep 9, 2011 at 2:08 pm

    “[...] to help us plan what needs to be images and what can be CSS in the final coded design.”

    You said it all. That’s what I’m looking for!

Leave a Comment:

Notify me of follow-up comments?



Join MediaLoot and Get Complete Royalty-Free Access

    Latest Freebies:

  • Free CSS3 Social Media Buttons
  • Free Vector Map Location Pins
  • Free Web Badges & Elements

MediaLoot on Facebook

MediaLoot is proud to be a part of the smashing network
  1. Sign Up for MediaLoot
  2. Download ANY resource from our collection
  3. Get tons of new resources every week