Apple is right to let Aperture go
After at first being a little surprised at Aperture’s demise it occurred to me that Apple is right to do this. Continuing to develop an app with small market share on an operating system with small market share makes little sense. It is better for them to admit defeat and try something better then continuing to go down the wrong path.
The technology landscape has changed a lot since 2005 when Aperture 1.0 came out. There are different ways to access files such as sandboxing and iCloud drive. These technologies will become an important way to get photos between a Mac and an iOS device. Tagging files in Aperture was helpful but relying on the tagging system built into the OS would be a much better solution (someone else just mentioned this recently and I strongly agree.) If a new pro photo app made it’s tags available to the Finder and Spotlight those tags should show up along side similarly tagged files that were created in other programs.
Also Aperture’s competition from Adobe is fundamentally flawed. An all new pro app could address the problems that Adobe’s photography apps have. Anyone who has used Adobe’s solutions should be well aware of their shortcomings.
1. Photoshop, which came into being in the 1980s, was not built around technology like raw and therefore requires a rather clumsy workflow.
2. When a document gets exported to Photoshop the user is presented with a confusing array of choices as to how that photograph should be handled. Each option with it’s own series of advantages and drawbacks.
When a photo gets brought back into LR after being edited in PS it creates a new copy. If that photo then gets edit a second and third time it just keeps creating more copies of the image. The same problem can be said of adobe camera raw.
4. I always thought it was a little odd that you have to export an image from LR in order to use it in another app. App’s like LR, Aperture, and Photos are file navigation programs so why do I need to bring a photo from one navigation program (Lightroom) into another navigation program (the Finder) in order to work with it? Yes, I realize that at times you may need a smaller resolution file of an image like for a webpage but why can’t I just make a smaller version from within the photo navigation program and keep the images all in the same app? Doesn’t make sense to me.
It doesn’t have to be this way. Modern apps like Pixelmator are similar to PS except they can handle raw directly from within the app. It seems like it would be possible to team up with Pixelmator so that a raw photo could go between the two apps while keeping all their settings in tact and not requiring users to make unnecessary duplicates of exported files. For an example you could change the brightness in Apple’s Pro app and then it would still stay at the same setting in Pixelmator. And then if you changed the brightness again in Pixelmator the adjustment bar setting would be brought over to Apple’s Photos.
Since Pixelmator didn’t exist when Aperture 1.0 came out the two companies were not able to unify their two products. When you start over with a new product considerations like this can be taken into account. One of the things I hate about Adobe’s photo apps is the way that a lot of modern technology like raw feels very tacked on (because it is.)