Adobe’s ‘Modern’ User Interface Is Just Webpages ⇥ unsung.aresluna.org

Marcin Wichary did a wonderful job of poking through a few of the dialog boxes revised by Adobe in recent versions of Photoshop and — surprise, surprise — they are not good in lots of pretty rudimentary ways:

I know I brought up that an existing power user base can be a huge pain in the ass, and I am a decades-old Photoshop power user. But this is different than other examples where the product needs or at least wants to evolve past its core audience or toward a different market. For Photoshop here, nothing I see indicates any change in course or clientele – and yet all of these good moments in UI that used to help me out no longer exist.

Plus, all those transgressions are solved problems. Those issues are not buried in pages of heavily litigated patents, or in seven collective brains of world-class interface designers whose driveways are presently occupied by cash-filled trucks sent over by frontier companies. This isn’t some long lost art that requires archaeologists to decipher. This feels like carelessness and laziness in face of basic UI engineering; in a likely internally-motivated effort to refresh the interface, the team threw an entire nursery worth of babies with the bathwater.

If you do a little poking around in Adobe’s application bundles, a key reason for the jankiness of these user interfaces becomes apparent: it is because they are little webpages. These dialog boxes are HTML files that reference a chunky CSS file and oodles of JavaScript, and appear to be built with React.

This is loathsome.

There are people out there who will insist it is unfair to blame the tools and that bad user interfaces can be built in entirely native languages, too, which is true. Also, Adobe’s interface has always been unique and not quite at home on either MacOS or Windows. Maybe it really is possible to build a web app that feels platform native. But I have never used one — not once — and for this mess to be increasingly used in the industry-standard professional suite of creative tools is maddening.

There are good reasons why Adobe is ridding itself of allies, and this is one of them. I was going to write about how this stuff should have been tried with people who actually use Adobe’s apps in a high-pressure environment, but I am sure it was and, also, it does not matter. Wichary has it right. These are fundamental principles of user interface design that Adobe is ignoring because its internal tooling has taken precedence.

See Also: Michael Tsai’s link roundup.