unsorted bits & pieces from Ale Muñoz, design hacker & freelance librarian
“As I’ve noted for nearly 20 years, the Japanese camera makers don’t exactly have the best marketing departments in the world. Far from it. So they launch something with words like “Meet the new flagship of the Coolpix Advanced Performance collection” instead of “High-end DSLR image quality in a camera that fits in your pocket.” Not that such a line fixes Nikon’s price problem, but it at least explains why you’d want one.”
Humor nerdo (visto por ahí, probablemente en Facebook)
“the work of gardening the conditions needed for healthy living systems to grow (familes, cities, companies, neighborhoods, food systems, ecosystems, energy systems, etc.) requires new ways of understanding and new ways of creating”
If it caught you by surprise, you weren’t paying enough attention, as the writing’s been on the wall for the last three releases (CS4 was crap, CS5 added some minor features, and CS6 was nothing more than cosmetic changes).
So now you’re wondering: what’s next? What tool should I use now that the best tool for the job of screen design is no longer a safe bet?
Here’s a thought to get you started: what if you rethink your process?.
What you call “screen design” is actually a collection of tasks, and if you think a bit about them you’ll see they can be classified in two (rough) groups:
tasks related to “micro” design (also called “details”, “pixel perfect” or “pixel fucking”), and
tasks related to “macro” design (think “layout”, “page design” or “grid hacking”)
Fireworks had the rare trait of doing both decently, so it made you forget that they’re actually different beasts, but its death signals a good time to think about different tools for different purposes.
If this reminds you of the UNIX philosophy of “small tools that do one thing well”, it’s not a coincidence. I’ve been thinking long and hard about this for more time than I’m willing to recognize in public, and the only conclusion I’ve arrived to is this: monolithic tools for design are the wrong choice. Choose one, and once your vendor announces its discontinuation you’re doomed.
Having a collection of small tools for different purposes not only keeps you safer, but also allows for incremental improvements of your workflow. Better, faster, cheaper (or even free) tools can replace your original choices, thus letting you improve your process bit by bit.
Yes, it might be a bit more complex. But it pays in the long run. It also saves your ass, as it is much easier to find a replacement for a small tool than for a mammoth like Fireworks or (gasp) Photoshop.
So… what’s my current weapon of choice, I hear you ask?
These days I’m quite happy with a combination of Sketch for micro design, and hand-coded HTML for macro design (this is actually an oversimplification, as my workflow is a bit more complex than this, but it helps illustrate the point).
Sketch is not without its faults (it lacks many features I loved in Fireworks, like master pages or a symbol library) but you can overcome most of its limitations using tools intended for “macro” purposes. HTML is a perfect fit, but other options worth considering are InDesign, Illustrator or Axure / OmniGraffle.
If you’re not yet ready to make the switch from a monolithic app to a combination of small tools, here’s my advice: make backups before every major operating system upgrades. One of them might kill your perfectly useful Fireworks. It happened with Freehand, and still miss it to this day…