Agentic AI
UX Veteran Scott Jenson Challenges Two Decades of Desktop Stagnation
The Macintosh and Chrome designer argues that operating systems have prioritized ecosystem lock-in over user productivity, while exploring how local-first architecture and context-aware interfaces could reshape computing.
InfoQ
Scott Jenson, the veteran UX designer behind innovations in macOS, Google Maps, and Chrome, recently examined why desktop operating systems have largely stalled in meaningful evolution. His argument centers on a troubling shift: instead of enhancing what users can accomplish, vendors have focused on tightening ecosystem control and maximizing lock-in.
Two Decades Without Progress#
Modern desktops have remained fundamentally unchanged for approximately 20 years, according to Jenson's analysis. While Apple has rolled out around a dozen features in the past 15 years, these additions—universal clipboard, AirDrop, cross-device handoff—all serve to bind users more tightly to a single vendor's ecosystem rather than expand genuine productivity gains. Desktop operating systems have become a settled technology, with companies seemingly content to maintain the status quo rather than reimagine what users actually need.
Mobile Won the Consumer, Not the Professional#
The smartphone revolution captured consumer attention, yet it never solved the fundamental challenge of knowledge work. When multiple tech companies attempted to replace desktop workflows with tablets around 2015—Google even dubbed it "Tablet Tuesdays"—the experiments failed. Mobile and tablet interfaces excel at consumption: media, gaming, social content. But they lack the depth for complex, creative tasks. This distinction matters: mobile and desktop are not rivals competing for the same job. They serve different purposes, and pretending otherwise has led to compromised interfaces on both sides.
Local-First Architecture as Pragmatism#
Beyond philosophical concerns about privacy, a serious practical problem haunts cloud-dependent systems: connectivity fragility. When AWS experiences an outage or when users find themselves without internet access, cloud-first architectures become unusable. Local-first design flips this: users retain full control of their data, work continues offline, and the cloud becomes optional infrastructure rather than a mandatory intermediary. This approach addresses two concerns simultaneously—data sovereignty and resilience—making it relevant far beyond concerns of corporate surveillance.
