Table of contents

Generative interfaces that make the next step clear

Yander Editorial

Design & engineering

2 min read

A green flower rendered as an abstract digital form

Generated content can change from one request to the next. Navigation, ownership, and the meaning of the primary action still need to be understandable. A user should know which parts are a proposal and which parts have already changed.

In an editable workspace such as KIMEO, generation is followed by deliberate changes on a canvas. That distinction offers a useful starting point for any interface that mixes AI suggestions with precise user control.

Give changing content a stable frame

Keep navigation, the current task, and the primary action in predictable places. Generated content can vary without making the entire workspace rearrange itself.

A person should be able to recognize what has changed since the last interaction. Group new content and preserve useful context.

Make the proposed action inspectable

Show a preview before an action changes a document or sends information elsewhere. Let the user edit the underlying inputs and understand the scope of the change.

Choose controls that fit the work. A table is useful for comparing rows; a form is useful for collecting structured decisions; a conversation is useful for clarification.

Design a complete set of states

Include loading, partial results, missing evidence, and recovery in the design. These states should offer a useful next step in plain language.

Test the experience using long answers and empty results as well as the polished example. Flexible content needs deliberate boundaries.

Put this into practice

Explore the related work and delivery scope.

Give generated content a usable product frame

Share example outputs and the actions a user must be able to inspect, change, or approve.

Discuss an AI interface
UX/UI designBack to top

Found this useful? Share it forward

Frequently asked questions

Common questions about this topic

Should AI generate the whole interface?

Choose which variation helps the task. Content and suggested layouts can be flexible while navigation, permissions, and action controls remain predictable. Test the least tidy output before expanding the generated surface.

How do we prevent a generated screen from triggering an unintended action?

Keep proposed actions separate from execution. Show the affected record or content, require the appropriate confirmation, and bind that confirmation to the version the user reviewed.

What examples should we use to test a generated interface?

Use long text, empty and partial results, conflicting suggestions, unsupported actions, and a user returning to earlier work. Check keyboard access and narrow screens as well as the polished desktop example.

Keep reading

Related articles you might find useful

Give conversational interfaces a way back

Yander EditorialDesign & engineering
A green abstract geometric composition

Less friction, better mobile experiences

Yander EditorialDesign & engineering
An abstract mobile interface composition

How to Choose a Web Development Company in Guangzhou

YanderWeb design & engineering
Academic Asia responsive website redesign, an example of multilingual web work
All articles