Crash Report for “Adobe Fireworks CS4” by Jon Hicks
Poor Jon. If ever there were a man who didn’t need Adobe apps crashing for no good reason, this has to be him. And, although I use Adobe apps a fraction as often as Jon, I can still sympathize. Brother, can I.
I hate bagging on software developers (Jesus, it’s such hard and underappreciated work), but I’m baffled by where Adobe’s Mac BU is heading.
Each release of the Adobe apps I use (and used to so depend on) feels less stable, more bloated, and — easy as this was to overlook for a REALLY long time — increasingly less Mac-like. Or at least less OS X-like. They feel like sketches of OS X applications, drawn from memory.
Kinda reminds me of Microsoft in 1993 or whenever it was they released Word 6. It’s hard to call up a metaphor for how badly those folks ruined one of the most elegant applications I used and truly relied on to do my job at the time. It installed dozens of crufty extensions, looked just awful, and ran with the pluck and elegance of an incontinent grizzly bear with the gout. So I stayed with 5.1 until it died in my arms some time later that decade.
Also makes me further appreciate the work of people like Gus (Acorn), Buzz (PodWorks), and Keith (Scrivener). Sure, they’re vending software, but really they’re selling elegant little solutions to real problems. Even Scrivener — which does a LOT — has its by-design limits, as chosen by the auteur who made it. But each of the three apps works (IMHO) at exactly the level of scope needed for what each needs to do. And not a bit more. Plus, they’re each really fun to use. And…er…don’t crash so much.
This level of awesome doesn’t happen by accident or iteration or lucky lottery ticket. Each app’s a joy to use precisely because it’s built from scratch to solve certain problems real people have in a certain context — not to do everything for everyone and certainly not to fit into a “Suite” that was invented by some white-toothed Stanford grad who knows each app’s “Features & Benefits” bullets better than the needs of its battlefield users.
In a good app (or a good anything) the design and functionality are inseparable; it’s designed like this because it works like this because it’s designed like this….
To paraphrase that overquoted analogy about drilling holes vs. “being happy,” nobody wakes up today going, “Oh, I can’t wait to leverage the synergy of Adobe’s integrated suite of applications and services.” They go, “Holy shit. Now that my drive crashed, I hope I can get the only copy of my MP3s off this old iPod.”
Nobody uses bullets. Nobody thinks that way, and, I promise you, nobody works that way. Yes, IT departments may buy that way. But, I’m not an IT department. (Except, yes, granted, when a subtly enhanced OS update goes tits up)
It’s just that right now, the Adobe apps I use don’t feel like they’re made for anybody. Then they crash. Which sucks.
Yes, I do hate to bag on software developers, but, Jesus. If I were one of Adobe’s Mac guys (and, obviously, if I had the resources and mandate to do so) I’d do any of four-ish things (And yes, I realize trying to do all of them at once is paradoxical and impossible. Pick one.):
(Yikes. Can’t believe this started as a Flickr comment. Anyhow.)
Adobe. Guys? Love you. I know a handful of you personally. You may (as with my pals at MS) have close to zero control over any aspect of any of this. If so I apologize. Not trying to be a dick. But there’s two and only two scenarios here for anyone who claims they want to be taken seriously by the OS X community:
One (sometimes one of the extremely few) of the benefits of the annoyingly rabid Mac community is that we do talk to each other a lot, and we do absolutely have equivalents of pro wrestling’s faces and heels. Right now, Adobe is not regarded as a hero. No. Right now you’re the heavy guy from some country we don’t like who’s always with the folding chairs.
I get that Photoshop and Dreamweaver etc. are about a lot (LOT) more than one task for one user by one developer. But should they really feel this much like the opposite of that? Like some…stuff for some…user…in some…job via some…enterprise suite that….[Ooops. Need to go re-activate.]
That’s not how you make people look forward to double-clicking your increasingly austere icons.
Maybe you don’t want or need to be a hero to a bunch of portly men in Daring Fireball t-shirts. That’s understandable. And, in which case, yes, this is all beyond irrelevant. But, I’m assuming you want to do the right thing and that you want to reclaim your rightful place of honor within the community that, frankly, helped make you (yeah, I know you’re big competitors now, rah rah).
But, if you did want to be a hero — and wanted to again become relevant to the crowd I run with — it’d take a lot of work and a lot of listening, and the same kind of grinding dedication to making something awesome for real people that’s made folks like Gus, Buzz, and Keith (and Chock and Cabel and Steven and Wil and Brent and on and on and on) as successful and beloved as they are.
So, listen. As ever, if I can help or you wanna talk or you just want to have me in for lunch to tell me where I got it wrong, Dom’s got my digits and you’re an easy MUNI ride away.
Ohs and exes,
Merlin
P.S. Notice how it wasn’t until this sentence that I mentioned Acrobat? That’s because I’m a gentleman. I’m restrained. Plus, I hate bagging on software developers.
For a lesson in keeping an app powerful but super-easy (and Mac-like) to use, look at Birdfeed, Buzz and Neven’s Twitter app for iPhone. I mean really look at Birdfeed. If you weren’t the type to fiddle around, looking for power user bits, you might never realize how much you can do with this easy-to-use app. And if you’re not that type, you probably never need to, right? So they built it that way. Got it? Exactly. Sublime. ↩