Harshita Nimbal explains: The Evolution of AI UX

For 40 years UX meant one screen built once for everyone. Harshita Nimbal describes three acts: fixed interfaces, prediction and generation, and agents that collapse the interface into conversation, with the cockpit as a counterexample.

5:53 video3 min readWatch on YouTube

Harshita Nimbal, an AI product designer, looks at how artificial intelligence actually changed the way people use software. She sets the hype aside and focuses on the interface itself. For 40 years, she says, UX meant one screen, built once and shown to everyone. Then the screen started guessing. The video tells that story in three acts.

Act one: the fixed interface

The first act covers the era before AI, roughly 1984 to 2010, when every interface was fixed. The graphical interface matured, with icons, windows, menus and skeuomorphic buttons that looked like real switches. Every design decision was baked in at ship time, tested once, and shipped to millions unchanged. The same screen and menus went to a teenager and a surgeon alike, and the software had no idea who was using it.

Personalization existed, but a human had to notice a pattern and hard-code the exception. Design at that scale meant Nielsen's heuristics, style guides and A/B tests read by hand. Every rule the interface followed, a person had written down first, so the system could not learn and could only be told.

Act two: prediction and generation

In the second act the interface stopped waiting to be told and started predicting. One app and one code base now offered a thousand front doors. A recommendation model watches what you click, and the layout itself forks, so your home page is no longer identical to your neighbor's. Prediction arrived one keystroke at a time, through autocomplete, then predictive text, then a search box finishing your sentence. By the 2010s the guess became the whole homepage, and Netflix has hundreds of millions of front pages, each assembled live from what you tend to watch.

Generative interfaces go a step further. A model reads the request and assembles the components, copy and even the layout tree, generated anew for that ask. Vercel's v0 is one example, where a typed sentence produces a working interface that no human designed. It is a loop rather than a snapshot: your clicks retrain the model, the model reshapes the interface, and your next click retrains it again. The designer's job shifts from drawing screens to shaping what the loop is allowed to learn.

Act three: the disappearing screen

The logical endpoint is a system that no longer needs a screen. Menus collapse into a search field, and the search field collapses into a chat box, so every button becomes a sentence you type. Instead of navigating to a setting, you describe the outcome and an agent finds or builds the path. The video shows a real Claude screenshot as an example, where the sidebar holds history and files but the work happens in one box.

Beyond the chat box, the video describes an agentic interface as a workspace rather than a chat log, one where you watch the agent plan, call tools and check its own work, one visible step at a time. Its job is to narrate the machine's reasoning, not hide it.

The cockpit exception

The speaker also names what would make the argument wrong: a domain where a fixed, hand-built interface is better. An airplane cockpit is one. Every switch is identical every time for every pilot, on purpose. Predictability is the feature there. Flexibility wins everywhere else, but certainty is what is worth optimizing for in a cockpit.

Key takeaways

  • For about 40 years, UX meant a single fixed screen built once for everyone.
  • Fixed interfaces followed rules that people had written down in advance.
  • Prediction let the layout fork per person, as with Netflix's homepage.
  • Generative interfaces assemble the screen on request, as v0 does.
  • Agentic interfaces collapse menus into conversation and should show the agent's steps.
  • Control moves from the designer's hand to the model's judgment.
  • Airplane cockpits remain a case where fixed interfaces are better.

Try it yourself

Take one interface you use every day and ask Claude which of its screens are still hand-built for everyone, which already predict or personalize for you, and what it would look like as a single conversational agent. Ask Claude to sketch the static, predictive and agentic versions of one screen, and to say what your product would gain and lose at each step.

Chapters

  1. 0:00Introduction: How AI Redefined the Interface
  2. 0:20Act 1: The Fixed Interface Era (1984–2000s)
  3. 0:50Act 2: Prediction & Generative Interfaces (v0, Netflix)
  4. 1:30Act 3: Disappearing Screens & Agentic Workspaces
  5. 2:10The Cockpit Exception & Summary
Full transcript(auto-generated, with timestamps)

Introduction: How AI Redefined the Interface

[0:00]Hi, I'm Harshita Nimble, an AI product designer. This video is about how artificial intelligence actually changed the way we use software, not the hype, the interface itself. Here's the shape of it. For 40 years, UX meant one screen, built once, shown to everyone. Then the screen started guessing. Three

Act 1: The Fixed Interface Era (1984–2000s)

[0:20]Acts, the era before AI, when every interface was fixed. The era of prediction, when software began guessing what you do next. And the era now arriving, when the interface disappears into conversation. Act one. Before prediction, before personalization, decades where the interface was the same for absolutely everyone. 1984 to 2010. The graphical interface matures, icons, windows, menus, skeuomorphic buttons that looked like real switches.

Act 2: Prediction & Generative Interfaces (v0, Netflix)

[0:51]Every design decision baked in at ship time, tested once, shipped to millions unchanged. And here's the part worth sitting with. This exact screen, these exact menus, shipped to a teenager and a surgeon alike. The software had no idea who was using it, and it never asked. Picture the funnel. Every user enters the same front door, sees the same layout, follows the same three clicks to check out. Personalization existed, but a human had to notice the pattern and hard code the exception. Design at this scale meant Nielsen's heuristics, style guides, and a slash B tests read by hand.

Act 3: Disappearing Screens & Agentic Workspaces

[1:30]Every rule the interface followed, a person had written down first. The system could not learn, it could only be told. Act two. The moment the interface stopped waiting to be told and started predicting. One app, one code base, and now a thousand different front doors. A recommendation model watches what you click, and the layout itself starts to fork. Your home page is no longer identical to your neighbor's. Prediction crept in one keystroke at a time, autocomplete, then predictive text, then a search box finishing your sentence before you did. Small, cheap guesses running underneath every screen you already knew. By the 2010s, the guess

The Cockpit Exception & Summary

[2:10]Became the whole homepage. Netflix doesn't have one front page, it has hundreds of millions, each one assembled live from what you specifically tend to watch. Generative interfaces go one step further. The layout itself is no longer pre-built. A model reads the request and assembles the screen components, copy, even the layout tree, generated new every time for this one ask. Compare the two build processes side by side. A designer's fixed component tree versus a model choosing components from a library on the fly. Same building blocks, but nobody wrote the blueprint in advance. Tools built entirely on this idea now exist. V0 from Vercel is one of them. Type a sentence and a working interface appears, never designed by a human hand at all. What's behind me is its direct output for one prompt, and it's a loop, not a snapshot. Your clicks retrain the model,

The model reshapes the interface, and your next click retrains it again. The designer's job quietly shifts from drawing screens to shaping what the loop is allowed to learn. Act three, the logical end point of a system that can guess and generate, it stops needing a screen at all. Watch the toolbar itself start to vanish. Menus collapse into a single search field, then the search field collapses into a chat box. Every button that used to sit on the screen now just a sentence you type. One text box replacing an entire menu tree. Instead of navigating to the setting, you describe the outcome you want, and an agent finds or builds the path there for you. This is what that looks like today, a real screenshot of Claude, not a mock-up. The sidebar still holds your history and your files, but the work itself happens in one

Box. Whatever you want, you just type it. We asked Claude to sketch what comes after the chat box, an interface for an agent that acts, not just answers. An agentic interface isn't a chat log, it's a workspace where you watch the agent plan, call tools, and check its own work, one visible step at a time. The interface's job becomes narrating the machine's reasoning, not hiding it. Here's what would make this whole argument wrong, a domain where a fixed, hand-built interface is still the better choice. And one exists, an airplane cockpit. Every switch is identical every time for every pilot on purpose. Predictability is the feature, not the limitation. Push it to its end point, and the interface stops being a place you visit. It becomes a layer that meets you inside whatever you're already doing. 40 years of UX bends toward disappearing. Everywhere flexibility beats

Certainty as the thing worth optimizing for. Let's recap with Claude. For decades, one interface served everyone, hand-built and hand-tuned. Then prediction let the interface fork per person. Generative models let it assemble itself on request. And now agents are collapsing the whole thing into a conversation that acts on your behalf. The through line, control keeps moving from the designer's hand to the model's judgment. Your turn. Take one interface you use every day and ask Claude, which of its screens are still hand-built for everyone, which ones already predict or personalize for you specifically, and what would it look like as a single conversational agent instead? Ask Claude to sketch all three versions of that one screen, the static one, the predictive one, and the agentic one, and tell you what your product would gain and lose at each step. How AI changed user experience. I'm Harshita Nimbolkar.

More from Humanitarians AI Fellows

Humanitarians AI Lyrical Literacy Project