Adobe, Macromedia & Fireworks

There has been a lot of dis­cus­sion in blogs and news­groups fol­low­ing the recent clos­ing of the trans­ac­tion for the acqui­si­tion of Macromedia by Adobe. I have been read­ing a lot about it in the last few days, offi­cial words and com­men­tary alike and there’s one thing that’s really been bug­ging me in many of the coments I’ve seen.

There’s a lot of peo­ple who seem to be con­fused about what Fireworkis is or what it can do. They spec­u­late that Fireworks is doomed because it’s not as “strong” as Photoshop or worse, because it “com­petes” with ImageReady. Both state­ments are dead wrong.

First of all, Fireworks is fun­da­men­tally dif­fer­ent in nature than both Photoshop and ImageReady as it is a true vec­tor based appli­ca­tion (not a raster appli­ca­tion with awk­ward vec­tor fea­tures tacked on like Photoshop…). Fireworks’ bitmap tools indeed do not have the depth of Photoshop’s but it doesn’t have the same pur­pose either. Fireworks was designed for the cre­ation of Web graph­ics only. It does not have Photoshop’s print her­itage. There is really no direct com­par­i­son between the two apps other than they their shar­ing some func­tion­al­ity and both are used to cre­ate Web sites graph­ics (although I really can’t think why any­one would sub­ject them­selves to the tedium of lay­ing out a Web site in Photoshop…).

Secondly, com­par­ing Fireworks with ImageReady makes even less sense despite what many peo­ple seem to think. ImageReady is really noth­ing more than a glo­ri­fied slic­ing, opti­miz­ing and export­ing tool and while those tasks are cer­tainly part of what Fireworks does they’re only a frac­tion of its func­tion­al­ity. Fireworks is first and fore­most a cre­ative tool whith which you design site lay­outs and graph­ics, not a mere “slic­ing and dic­ing” tool used after the “real” work gets done in a more sophis­ti­cated appli­ca­tion like Photoshop or Illustrator.

With Fireworks there is no mid­dle man, you cre­ate then slice then opti­mize and pre­view graph­ics right within the same inte­grated and effi­cient inter­face with pre­cise and flex­i­ble vec­tor as well great bitmap tools. Regardless of the innacu­rate infor­ma­tion some are spread­ing about Fireworks and beyond all the spec­u­la­tion sur­round­ing the acqui­si­tion and plans for spe­cific prod­ucts, I choose to hope that Adobe will be smart enough to rec­og­nize the unique nature of Fireworks and keep it around and develop it fur­ther. Fireworks really should have a future and deserves bet­ter recog­ni­tion than what it got under Macromedia’s inept mar­ket­ing efforts on its behalf…

If you liked this article, get updates (it’s free).

, , , ,

5 Responses to Adobe, Macromedia & Fireworks

  1. P. Brown January 26, 2006 at 6:01 pm #

    If Adobe gets rid of Fireworks, they are totally nuts. I will NOT switch to image ready or Photoshop. I love Fireworks!

  2. Peter Tilbrook February 14, 2006 at 12:02 am #

    Hear hear! But it seems Adobe are keep­ing Firefox so woo hoo!

  3. Improve February 27, 2006 at 7:02 am #

    Yes.I like Fireworks!

  4. Jason Holden May 16, 2007 at 7:05 pm #

    I use Fireworks for all my web graph­ics, but you would be sur­prised at the num­ber of tem­plates that I get in PSD format.

  5. Stéphane May 16, 2007 at 10:05 pm #

    I’m not sur­prised Jason, I get PSD files all the time too. But I still don’t under­stand why so many design­ers choose to do design and lay­out work in Photoshop. If Fireworks didn’t exist, I’d prob­a­bly be using Illustrator or FreeHand to do the same work. Photoshop is a ter­ri­ble choice for lay­out work. Any vec­tor based app is much bet­ter suited for it IMO.

Leave a Reply