Apples decision to completely rewrite Final Cut Pro has been met with a lot of mixed opinions. John Gruber has a summary of the backlash here -http://daringfireball.net/2011/06/final_cut_pro_x_backlash
It seems clear to me that it was done in order to ultimately progress the app, extend it’s future and no doubt update what was a legacy code base. It will have been this update in legacy code that will have meant some features have been lost (for now). It’s a bit like those uncluttering techniques where you chuck everything out and then slowly reintroduce things as it becomes obvious that you need them. A risky approach perhaps but the long term benefits should out way the short term niggles.
Adobes Photoshop feels and performs like an app that needs this kind of attention and approach, you just need to look at apps like Pixelmator & Acorn to see what could be achieved starting from scratch and utilising the OS it’s made for.
Photoshop feels like a Frankenstein app, lots of different parts cobbled and stitched together to make a lumbering and stumbling collection ofiInconsistent dialogs and behaviours. I wonder if the developers have ever played Buckaroo
Wow, this is amazing. How can this still exist in Dreamweaver?
Adobe really need to follow Apples lead and do what they did for Snow Leopard. Release their next major version with little or no new features. They really need to just rip out the crud, refine core features and then rebuild their apps from scratch. They also need to bite the bullet and make it native for each OS. This one for all approach just never works in any environment.
Dreamweaver: Long history of faking interfaces at Adobe, you can tell because OS X looked like that 9 years ago.
Looking at this and the crappy bits of UI thrown together in Flash these days I just want to ask the question: Whats so fucking difficult about programming some combo boxes and check boxes properly? I’m sure they must spend more time at Adobe figuring out ways to get around just programming this shit properly than they would have done just programming it correctly and native in the first place.
Thanks Marcus
An HTML5 animator built using an HMTL plug-in technology. Not sure if that’s ironic or not… but I suppose it’ll keep people buying adobe products right?
Now this is more like it Adobe, a demo of a new HTML5 animation editor.
Looks impressive but from the demo the UI appears to be Air or similar to the Flash parts of the Flash IDE, judging from the dodgy tooltips and font rendering. Now thats perfectly fine for a prototype, but from my experiences with the non-native elements of the Flash UI and the Fireworks UI are horrible to work in.
I’m not saying all UIs should be Aqua or Aero, I mean I love the After Effects UI. I’m just saying they shouldn’t be running in a vector engine originally designed for cartoons and slideshows.
From All Things Digital
John Paczkowski: Cross-platform mobile apps tend not to take advantage of native features unique to each device. What do you have to say about complaints that write-once-run-anywhere software results in subpar apps?
Chuck Geschke: Well, people don’t say that about Photoshop. They certainly don’t say it about Acrobat…. I’m a little confused about what the real examples of that are.
My inbox says different Chuck…
Mental. OK this looks great, the amount of tech that went into this is probably mind blowing. Now if the same techs worked on consistent UI and ironing out bugs from the Adobe suite that would definitely be worth the upgrade.
via strake:
A preview of Photoshop’s upcoming content-aware fill and delete features. Stick with the video as each demo gets more impressive. This alone probably makes the CS5 upgrade worthwhile.
I gave up filling them in, but maybe I’ll start again…
via maniacalrage:
I always write really long, winding complaints in the Adobe Crash Reporter. I hope someone at Adobe is forced to read them. This one makes a lot more sense than most of them do.
I always chuckle at these gripes but it saddens me as well. I use their software on a daily basis and come across “gripes” almost every time I use them. Adobe have the potential to make their apps better than any other on the market, yet the indie app makers like Panic, Flying Meat and MacRabbit beat them every time due to their attention to details, incremental updates and listening to their customers. With the next release of the Creative Suite they need to focus on getting all their UI consistent and getting shot of all the bugs and making it all lean. Take a year out, heck take 2 or 3 I can live with that as long as what I get at the end is useable, up to date and doesn’t hang because it feels like it.
Dreamweaver: Hey Dreamweaver team, in case you were wondering why you had become completely irrelevant
Thanks Dan
Not something I’d immediately picked up on but with so much visual noise in these apps today thanks to the myriad of options it’s good someone’s taken the time to point this out. Whether it leads to anything is another thing.
I did not mean to write an essay detailing all the ways in which slider controls in Photoshop CS4 reveal problems in the design, development, quality control, and management of the product; I really didn’t. I just pulled up the Smart Sharpen dialog one evening and, sighing at its hideousness for the nth time, decided to put together a little joke post. That was all.
Is there an Internet rule yet stating that even the most obviously indefensible mistake will eventually be defended by someone somewhere? Awful marketing efforts get explained as genius viral campaigns, broken features become solutions.
So, several people wrote to yours truly picking on one single item from my post: the sliders’ deviation from OS X’s standard. The defense being twofold, it seems:
- Photoshop’s sliders are different for a reason, and
- Hey, Apple does custom controls too, so it’s alright.
To which I say:
- No they’re not; not as a rule, anyway. There’s no reason for Memory Usage, Brightness, Pencil Width, Radius, and Scale to be different from each other. They all do the same exact thing: pick a single value from a range. (Needless clarification: yes, Scale has to be a bit smaller to fit comfortably in its window. Making well-fitting smaller versions of controls shouldn’t be rocket science.) These make up more than 50% of my examples. What’s the explanation for those?
As for the remaining custom controls, they do more than pick a single value, so they should be different. But… this different? Why are the Threshold and Color Balance sliders aliased when Layer Blending isn’t? Does anyone find these well-rendered?- When Apple deviates, they usually innovate. When they introduce a new slider (like the one in iTunes 9) it’s an improvement. It feels at home in its window.
However, Apple is sometimes wrong. Final Cut Pro - originally designed by Macromedia - is not Apple’s finest UI hour. Children learn at a young age that bad behavior isn’t excused by saying “Cathy did it too!”(I have now written way too much about all this. Aren’t these flaws simply obvious?)
I’m not saying anyone at Adobe is evil or crazy. I thought it was, in fact, pretty clear why Photoshop’s sliders are an unappealing mess: they were designed by someone who shouldn’t have been designing, implemented by someone who should’ve been implementing better, skipped over by someone who should have been finding bugs, and approved by someone who should have had higher standards.
It’s not the end of the world that a thumb control is misplaced by one pixel. All software ships with bugs, or it doesn’t ship. But here we are, version 11 of the app, and one of the most-used standard controls in the app is broken.
And this is only sliders we’re talking about. If this dead horse needed any more beating, I’d put together a gallery of misaligned text labels, inconsistent popup buttons (often in the same window!), badly scaled controls, and nearly impenetrable UI bugs. (I mean, there’s a whole blog for these.) What’s the explanation there - is that innovation? Or is it simply the case that this doesn’t matter enough to Adobe?
I love Photoshop. It’s where I spend eight hours five times a week. I just wish that one of these days, instead of piling on more furniture, they’d clean up the place.
Can’t imagine we’ll be getting Flash on the iPhone anytime soon then…
via adobegripes:
Adobe gets bitchy over the iPhone and Flash, bit of an insight from the reddit thread :
About six months ago, a friend who was working closely along side adobe’s flash application development team told me that they received a prototype of Flash for iPhone. The prototype allowed the iPhone to have less than half an hour of battery life using flash. They then sent the prototype to apple and suggested incorporating this prototype iPhone flash into the iPhone OS in the next update.
Apparently apple sent this letter back thanking them for being interested in developing a working version of flash for the iphone but because the prototype is so processor intensive, and awful for battery life, they would not include it with their OS because it is just not good enough. They suggested using the gpu instead of the processor to render flash. Then they suggested building a seperate app for flash and web browsing because there was no way apple could endorse flash integration on the iphone in its current state.
Adobe apparently didn’t want to release the app under their name either and it never showed up in the app store.
A long story in short: Adobe sucks at programming, then apple told them they sucked at programming. If they want to release that shit under the name adobe so be it, but it sure isn’t going to be endorsed by Apple.
That was the last they saw of that prototype.