iPhoto for iOS was released on the App Store earlier today, and after an enthusiastic introduction at Apple’s media event in San Francisco, the latest photo editing app from Cupertino received a controversial “welcome” on various blogs and Twitter streams as users got their hands on the all-new interface and photo management system. So what’s all the fuss about iPhoto for iOS?
I have been trying the app on my iPad 2 and iPhone 4S (running iOS 5.1, of course, as it’s a requirement) for the past few hours, and I think that it is very powerful. As I’ll illustrate in a bit, Apple did manage to squeeze some advanced photo editing and refinement technologies in the mobile version of iPhoto, putting it on the same level if not above iPhoto for Mac when it comes to editing, making quick adjustments, and interacting with your photos. Once mastered, the new gestures and tap commands can be quite powerful, although the app can have a steep learning curve. I also believe, however, that iPhoto for iOS suffers from a serious file management problem, in that it’s the best example of iOS’ lack of a centralized file system where apps are able to easily “talk” to each other and share files or modifications to them.
I want to get this out of my system before I get to the (very) good stuff. If you were hoping to see Apple coming up with an effortless way of importing photos avoiding duplicates and manual management, well, I’m sorry, you’ll be disappointed with iPhoto for iOS. This version of iPhoto is yet another data silo that is self-contained, and won’t simply “sync” the changes it makes to photos out of its closed environment.
I say “simply”, because there are exceptions in iPhoto for iOS, as it doesn’t use the exact same system of iPhoto for Mac when it comes to finding photos on your device. Because iOS devices come with a systemwide “Camera Roll” that’s accessible by other apps, Apple engineers had to make sure iPhoto could access such location – and here’s where I started to run into issues. Read more