A big-assed post about Fireworks

01 Oct 2009

This is a post about Fireworks. Not about Photoshop, Illustrator and which is ‘best’. This is about a frustrated love hate relationship.

I love Fireworks.

It’s been my tool of choice for a rather long time. In the previous year of working for Opera, I’ve used it more than any other app. Whether I’ve been working on interactive wireframes, UI mockups, icons or final production artwork, Fireworks is the one that I go to.

When people ask why I don’t use Illustrator or Photoshop I sometimes find it hard to articulate precisely why. Illustrator is undoubtedly best for print/high-res illustrations and logos, while Photoshop is the first choice for manipulating photos, especially for print. Each have some tools from the other, but neither is intended for creating screen graphics with vector and bitmap tools in the way that Fireworks is.

It loves pixels. Photoshop and Illustrator only ‘do’ pixels when they’re coerced, and by golly do they take persuasion sometimes. For example, in Illustrator, why does a 1 pixel stroke on a pixel perfect box, placed on pixel perfect co-ordinates have sub-pixels on the top edge? Why do I have to make the stroke 0.9px instead of 1px just to get a crisp 1px edge?

Screenshot of the 1px border bug in Illustrator

This is surely the most basic of things to get right? Photoshop can do vectors and some of what Fireworks can – it just makes it harder to do it.

What’s so great about Fireworks…

Pixel-snapping vector tools aside, it’s most useful feature (that still isn’t present in anything else I’ve tried) is multiple Pages and States. Why have 45 separate files for a set of icons, when I can have one file that will export to 45 individual files? Let’s say all these icons have the same background, like a typical OS X toolbar button, and you notice a glitch. To update all those files would be tedious, but because it’s in Fireworks on a shared layer (or Master Page) one update is all that is needed. Master Pages in particular come in handy with site designs, as each page can be a different size and canvas colour.

Here’s a sample working file of Opera Unite icons:

Fireworks

It contains five different pages (one for each pixel resolution) and 10 icons per page, each on a different ‘state’. 50 icons, one file, one export. I’ve attempted replicating this functionality with layers, layer comps and multiple artboards, but they don’t come close.

Every time I’ve worked on wireframes and mockups, I’ve felt blessed that I’ve got symbols. Anyone that’s used Flash will know what a symbol library is, but for those that haven’t, think of them like this: Reusable content. Take the example of a form button in a site design. I can create a button symbol, specify how that graphic can be resized (with 9 slice guides), and place it anywhere in my document. Again, updating and editing is a do-once, update every instance affair.

It’s not all roses though.

I also hate Fireworks.

With a growing passion. With each update we get more tools and features that I care nothing for – Adobe Air, Bridge and Flex integration and CSS export. Worst of all it’s become remarkably unstable, particularly under Snow Leopard. It crashes, even when you don’t look at it funny.

I use it because it’s the best there is, but there are a lot of holes that need filling for me:

I really could go on, but there are also more general problems with the Adobe Creative suite:

Compare these gripes with an app like Opacity. It downloads quickly, you open it and it asks you if you want to place it inside the Applications folder – done! That’s installation. As for updating, it self-updates and lets you know what’s been changed. The least amount of friction, and you’re left with the feeling of being in control of what you’ve installed.

Now, at this point, I need to confess that I’m the worlds worst beta tester. I’ve been on Fireworks beta programmes before, but haven’t had much time to give feedback or bug reports. So it’s a bit rich of me to be whining on my blog when this is all feedback that should’ve been submitted.

The problem is, after submitting the 20th crash report of the day, I’ve lost faith that anyone ever sees them or acts upon them. Overall, it feels like Fireworks is at the point of no return – no hope of it ever being fixed or improved, only that it will get more bloated, buggy, non-native and expensive. A stable version will no doubt come, but we will have to pay for it in the form of CS5. Maybe it’s not the Fireworks team that’s the problem here, maybe it’s higher up at Adobe? Maybe it’s just my setup? I can’t tell.

The bottom line is: Fireworks was my favourite, cherished tool, and it’s unreliability and issues mean my daily workflow is badly disrupted.

So, my thoughts turn to competitors. I’m not the only one, others are fed up with Fireworks and are looking for something to use instead. John Gruber, using the analogy of Filemaker’s Bento app, hits the nail on the head:

Adobe shouldn’t scrap its existing software any more than FileMaker Inc. should scrap FileMaker. But where’s Adobe’s “Bento” for bitmap and vector image editing for the Mac? The Bentos in this space are coming from indie developers with apps like Acorn, Pixelmator, Lineform, and Opacity.”

For such a long time, there haven’t been any alternatives. Various apps have been born that compete with other Adobe Suite apps, like Lineform and VectorDesigner with Illustrator, and Pixelmator and Acorn with Photoshop. Nothing for Fireworks, and yet the need for screen graphics is surely growing daily? Not only with websites, but desktop software and mobile apps.

In the meantime, Twitter clients have become ten a penny and Omnigraffle has matured to become a truly great tool for multi-page wireframes.

Recently however, three potential alternative apps have surfaced: Drawit, Acorn 2 and Opacity. I’m going to be putting these apps through their paces, to see if they can be potential alternatives. That’s for another time though, as this post has gone on long enough!

However, initial trials are showing Opacity as the most thoroughly feature-filled contender, but with Acorn sporting undoubtedly the most thoughtful interface. Acorn also has the advantage in that it’s developer, Gus Mueller, is actively seeking feedback on how it can be more of a Fireworks competitor. Drawit also has a pleasing UI, but with some issues on rendering.

I’ll report back on these when I can!

Recent Posts

It’s just fashion

26 Jun 2018

The Symbol Sourcebook

08 Jun 2018

Differences between Icon and Logo Design on This is HCD Podcast

10 Apr 2018

Twelve South PencilSnap

01 Apr 2018

The Infinite Canvas

09 Feb 2018

Blade Runner 2049

14 Oct 2017

Instagram Hickstagram

  • 14 Aug 2018

  • 14 Aug 2018

    Everything’s going to be OK!

  • 14 Aug 2018

  • 12 Aug 2018

    Curry wurst, at last!

  • 12 Aug 2018

    Wheels new and old

  • 11 Aug 2018

    Exploring Nuremberg 🤗

  • 11 Aug 2018

  • 11 Aug 2018

  • 11 Aug 2018

  • 11 Aug 2018

    A real highlight of Nuremberg!

Contact us

Call Jon on +44 (0)7917 391536, email or tweet @hicksdesign.

Alternatively, pop in for tea and cake at the studio…

Hicks
Wenrisc House
Meadow Court
Witney, OX28 6ER
United Kingdom