The Shift: From Designing Interfaces to Engineering Experiences

Main point: AI is closing the gap between design intent and real software, so designers are moving from drawing interfaces to building experiences in code.

Where I'm coming from

I'm building Unplanned OS, a browser-based personal OS on Next.js with draggable windows, a dock, an app launcher and a Cmd+K palette. Designers don't hand over screens. They ship their own apps into the shell, using the same Radix, Tailwind and Zustand patterns as everything else, with Cursor, skills, scoped zones and plans alongside them.

Shifting right

Connecting Figma and the IDE with AI moves designers closer to what users actually touch. That gives:- Realistic validation: ideas meet real layout, persistence, scrolling and themes, not frozen fake data- Faster feedback: production-like chrome in minutes, not weeks waiting on a slice- Production-ready thinking: specs become implementations you tighten, not pictures engineers redraw

Beyond the static canvas

This isn't designers doing mediocre engineering. Agents handle the boilerplate (a new window route, wiring into apps.tsx, tests) while designers own architecture, ergonomics and tone. Narrow task scope and clear boundaries stop it turning into churn. The craft moves towards curation: stating intent, constraints and acceptance criteria, then refining.

Closing

The goal isn't just speed. It's meeting honest friction early: tokens, keyboard paths, persistence, resizing. Interfaces were the deliverable. Experiences in real software are the new baseline.