It has been a crazy few days, following Adobe’s announcements about the new Lightroom(s) and the Creative Cloud. There is a lot of fear, uncertainty and doubt circulating, but that will die down over the next few weeks, as photographers on Adobe’s Photography plan play around with both the updated Lightroom Classic and the new Lightroom CC. (If you want an encyclopedic overview of everything regarding the Lightroom announcements, The Lightroom Queen is the place to go, to be honest.)
If you’re a user, looking at these announcements from the outside—i.e. you’re not a software developer—it can be difficult to understand why Adobe did what they did with Lightroom. Peter Krogh, an expert on digital asset management (DAM), has a fascinating post over on his website, entitled Lightroom and the Innovator’s Dilemma.
“But the architecture of Lightroom as a desktop application simply cannot be stretched enough to create a great mobile application. The desktop flexibility that has powers such a wide array of workflows can’t be shoehorned in to full cloud compatibility. The freedom to set up your drives, files and folders as you wish makes a nightmare for seamless access. And the flexibility to create massive keyword and collection taxonomies does not work with small mobile screens. After years of experimentation, the only good answer was the creation of a new cloud native architecture. As with the creation of the original Lightroom, this was done by taking the existing Camera Raw imaging engine and bolting it on to a new chassis – this time a cloud native architecture.”
Peter’s post is worth reading, especially if you’re confused or upset about Adobe’s direction. You might not like what Adobe did, but they are doing what any company must do if they wish to remain relevant: juggle the current (and future) needs of their users with the changing dynamics of technology, all while still trying to maintain a stable revenue (and profit) stream.