AI Can Build a UI in Seconds. What Happens to UI Development Now?

AI-assisted development is taking the frontend world by storm.

Throw a description of a dashboard, landing page or component at an AI coding tool, and it can churn out a working prototype in seconds. It can produce a variety of UIs - HTML/CSS/JS, React components, layout code, forms, variations of the same component, etc.

The obvious question asked by developers then, is

If AI can generate the interface, what is the job of a frontend developer?

AI is Good at Creating the Starting Point

The creation of repetitive UI code has never been the most exciting part of frontend development.

Buttons, cards, tables, navigation, forms - the whole nine yards. These are all common patterns that AI can be great at generating.

A developer can provide a description like:

"Create a responsive manufacturing dashboard showing equipment status, inventory levels, production activity and alerts."

An AI can potentially produce a decent first version of this.

But a first version is rarely a production-ready interface.

The hard questions come later.

What Information Should the Interface Actually Show?

For an industrial application, there are many sources of data that might be relevant to the interface:

IoT sensors, RFID, BLE, manufacturing equipment, ERP platforms, MES, LIMS, QMS, other applications. You name it.

There is no point is shoehorning all of this information into one dashboard - it's too much for any user to process.

The developer needs to determine what information is relevant to different types of users (operations manager, inventory clerk, quality controller, etc.)

It's all about context.

The interface is an information architecture problem, and not just a UI code problem.

AI Doesn't Know About the User

The generated interface may look nice, but it may fail to serve the real user - it may not help them in their day-to-day activities.

Imagine an AI-generated dashboard with twenty charts, all of which are working fine.

But if it takes the average user five minutes to find the information that indicates a production problem, has the computer really done its job?

The developer needs to determine:

What is the user's main job goal? What information is most relevant? What should be shown in greater detail? What should be highlighted? What to do if information is missing? How to present errors? How to make the interface function well on narrow screens? Is the interface accessible? What information should be visible/not visible based on permissions?

There's a lot that goes into context beyond just the information that needs to be shown.

The Developer's Job Is Changing

Frontend development with AI-assisted development tools may lead to changes in what the developer does. One possibility is that the developer moves towards the following areas in application development:

1. System Architecture

Rather than writing generic UI components, the developer spends more time figuring out how to organize the application - how components, APIs, state management, security, and databases will fit together.

2. Design Systems

While individual UI components can be generated by AI, creating consistent spacing, typography, accessibility, interaction design, responsive behavior and component architecture requires a design system.

3. Data Visualization

Industrial applications can generate a ton of information.

But just throwing it into a chart or table isn't enough to turn that data into information.

The developer needs to determine how best to visualize data as charts, timelines, alerts, tables, or other means that help the user get information from the data.

4. Edge Cases

The generated code may focus on the "main path", but there are always edge cases in production software. What if the user loses connectivity? What if an API returns an error? What if a sensor stops sending information? What if a permission is denied? How should the interface respond to these situations?

5. Domain Knowledge

This can be crucial for certain applications.

A developer who knows the domain of the application can better ask the right questions and see issues that a general-purpose code generator may not.

This is especially the case in specialized fields such as pharma manufacturing.

AIoT platforms in the space can connect asset intelligence, inventory intelligence, process intelligence and manufacturing traceability. PharmaFlux AI

The UI developer for such systems is not just writing UI code, they're helping users understand a complex operational world.

So, Is UI Development Going Away?

Not in the simple sense of "AI writes code, so developers are unneeded".

But the nature of the developer's job is changing.

The developer may need to spend less time on repetitive coding tasks, and more time on reviewing and enhancing the generated code, evaluating architecture, making sure the interface serves the user, testing the code's edge cases, connecting different systems, and determining what information should be shown.

The most important skills for the developer may shift from simply knowing how to write generic UI code, to understanding the application's requirements, making choices about its information architecture, and knowing if the generated code is really fit for purpose.

The developer still needs to understand the problem that the code is supposed to address.

Tell me what you think.

If AI can generate most basic UI components, what should frontend developers be focusing on?

UX design? System architecture? Accessibility? Performance? AI-assisted development? Domain knowledge?

I'd be interested to hear from other developers on how they see this space evolving.