Icon

UX

Icon

AI Wireframing for App Design: Our Claude Artifact Workflow

·

By Chandresh

Kraftbase thumbnail: AI wireframing for app design, guide

We stopped drawing wireframes and started shipping them.

We stopped drawing app wireframes in Figma. Now Claude builds the first clickable wireframe and the client changes it themselves. That's our version of AI wireframing for app design. We lock the flows and go straight to high fidelity, with fewer revisions and 70% less meeting time.

Here's the four step loop we use, how it compares with Figma, and where it falls short.

Figma wireframe loop compared with the AI wireframing loop for app design


Key takeaways

  • A Claude artifact is a clickable wireframe, so clients test a flow instead of reading arrows.

  • Clients make their own feature and flow changes by prompting Claude.

  • Big changes come out early, so there are fewer rounds overall.

  • Once flows are locked, we skip Figma wireframes and start high fidelity.

  • Keep it to flows, keep the styling plain, and check every locked flow with a developer.

Why did Figma wireframes slow app projects down?

Every change went through our designer. We’d show static screens in a call, the client would nod, and a week later send notes like “what if payment lived inside checkout?” Each note meant another redraw and another review call.

Most of that time went into deciding which feature belonged in which flow, with our designer acting as the client’s hands in Figma.

What is our AI wireframing loop for app design?

We call it Draft, Send, Steer, Lock. We do steps 1, 2 and 4. The client does step 3, and steps 2 and 3 repeat until the client says “this is it”.

AI wireframing loop for app design: Draft, Send, Steer and Lock, and who does each step

1. Draft

After kickoff we give Claude the brief, the main user flows and any real content, and ask for a wireframe as an artifact. An artifact is a working web page, so the client can click through it.

We keep it plain on purpose: greys, one accent color, boxes for images.

Pro tip: Ask Claude for two versions of any flow you’re unsure about. Letting the client tap through both settles the question faster than any call.

2. Send

We send the client a link instead of a meeting invite. They open it on a laptop or phone and click through it between their own meetings.

3. Steer

Clients don’t send us lists of changes anymore. They make the changes by prompting Claude, and see the result straight away.

A phone wireframe surrounded by the four kinds of change clients make in AI wireframing
  • A new feature: “Add a saved searches screen to the home tab.”

  • A different flow: “Make onboarding three short steps.”

  • A feature in another place: “Move payment into the booking flow.”

  • A whole app check: they tap through and find the dead end nobody spotted on paper.

Two rules keep it on track. Change flows and features, not styling. Send every change back as a link.

Pro tip: Put both rules in the first message you send with the link. Clients follow rules they read next to the work. They forget the ones from the kickoff call.

4. Lock

When the client is happy, we lock the flows and go straight from the artifact to high fidelity design. There’s no Figma wireframe stage in between. Because clients tested their ideas as they had them, there’s far less left to change by the time a designer opens Figma.

How does AI wireframing compare with Figma wireframes?

Question

Figma wireframes

Claude artifacts

What does the client see?

Static screens, in a call

A flow they tap through

How many rounds?

A new round for every set of notes

Fewer, because ideas get tested early

Meeting time

Baseline

70% less

The 70% comes from fewer revisions. Clients settle their flow changes while they try ideas, so there are fewer rounds of changes and fewer review calls to sit through.

What doesn’t work yet?

  • It can look like a real app. Some clients ask when they can log in. Plain styling and a “flows only” note fix most of it.

  • Claude doesn’t know your constraints. It will wire up features that are costly to build, so a developer checks every locked flow.

  • It’s not a design system. Nothing carries into the build. It’s a thinking tool.

  • You still need a designer. We review every version and push back on crowded screens.

  • Watch what goes into prompts. We agree with the client up front what we share with Claude, and leave out anything confidential, such as unreleased features.

It works best early, when the big questions are which features exist and where they live. For a product with settled flows and a strict design system, small changes are quicker in Figma. That’s why we use it to start new app projects in our SaaS UI/UX design work.

Also read: Onboarding and empty states for AI tools, AI SaaS dashboard design examples, How to choose a UX design agency.

AI wireframing FAQs

1. Can Claude make app wireframes?

Yes. Ask Claude for a wireframe as an artifact and it builds a clickable prototype, where screens link to each other and forms move to their next state. Keep the styling plain, so the conversation stays on which features exist and how users move between them.

2. Does AI wireframing replace Figma?

Not for us. It replaced Figma wireframes only. High fidelity design still happens in Figma, and our designers start it from the flows the client locked in the artifact, so there's no wireframe stage to redraw.

3. Does it really mean fewer rounds of changes?

In our projects, yes, because the big flow changes come out while the client is still trying ideas, not weeks later.

4. How do you stop clients adding features forever?

We review each version before anything is locked, and a developer checks it. A feature that's costly to build gets a conversation about scope and budget, not an automatic yes.

About the author

Chandresh is an engineer at Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.

How we know this

The Draft, Send, Steer, Lock loop is our own process, not a published standard.

Design call

Want your app flows wireframed this way?

Send us your app idea or brief and we will show you how this loop would work on your main flow.

We stopped drawing wireframes and started shipping them.

We stopped drawing app wireframes in Figma. Now Claude builds the first clickable wireframe and the client changes it themselves. That's our version of AI wireframing for app design. We lock the flows and go straight to high fidelity, with fewer revisions and 70% less meeting time.

Here's the four step loop we use, how it compares with Figma, and where it falls short.

Figma wireframe loop compared with the AI wireframing loop for app design


Key takeaways

  • A Claude artifact is a clickable wireframe, so clients test a flow instead of reading arrows.

  • Clients make their own feature and flow changes by prompting Claude.

  • Big changes come out early, so there are fewer rounds overall.

  • Once flows are locked, we skip Figma wireframes and start high fidelity.

  • Keep it to flows, keep the styling plain, and check every locked flow with a developer.

Why did Figma wireframes slow app projects down?

Every change went through our designer. We’d show static screens in a call, the client would nod, and a week later send notes like “what if payment lived inside checkout?” Each note meant another redraw and another review call.

Most of that time went into deciding which feature belonged in which flow, with our designer acting as the client’s hands in Figma.

What is our AI wireframing loop for app design?

We call it Draft, Send, Steer, Lock. We do steps 1, 2 and 4. The client does step 3, and steps 2 and 3 repeat until the client says “this is it”.

AI wireframing loop for app design: Draft, Send, Steer and Lock, and who does each step

1. Draft

After kickoff we give Claude the brief, the main user flows and any real content, and ask for a wireframe as an artifact. An artifact is a working web page, so the client can click through it.

We keep it plain on purpose: greys, one accent color, boxes for images.

Pro tip: Ask Claude for two versions of any flow you’re unsure about. Letting the client tap through both settles the question faster than any call.

2. Send

We send the client a link instead of a meeting invite. They open it on a laptop or phone and click through it between their own meetings.

3. Steer

Clients don’t send us lists of changes anymore. They make the changes by prompting Claude, and see the result straight away.

A phone wireframe surrounded by the four kinds of change clients make in AI wireframing
  • A new feature: “Add a saved searches screen to the home tab.”

  • A different flow: “Make onboarding three short steps.”

  • A feature in another place: “Move payment into the booking flow.”

  • A whole app check: they tap through and find the dead end nobody spotted on paper.

Two rules keep it on track. Change flows and features, not styling. Send every change back as a link.

Pro tip: Put both rules in the first message you send with the link. Clients follow rules they read next to the work. They forget the ones from the kickoff call.

4. Lock

When the client is happy, we lock the flows and go straight from the artifact to high fidelity design. There’s no Figma wireframe stage in between. Because clients tested their ideas as they had them, there’s far less left to change by the time a designer opens Figma.

How does AI wireframing compare with Figma wireframes?

Question

Figma wireframes

Claude artifacts

What does the client see?

Static screens, in a call

A flow they tap through

How many rounds?

A new round for every set of notes

Fewer, because ideas get tested early

Meeting time

Baseline

70% less

The 70% comes from fewer revisions. Clients settle their flow changes while they try ideas, so there are fewer rounds of changes and fewer review calls to sit through.

What doesn’t work yet?

  • It can look like a real app. Some clients ask when they can log in. Plain styling and a “flows only” note fix most of it.

  • Claude doesn’t know your constraints. It will wire up features that are costly to build, so a developer checks every locked flow.

  • It’s not a design system. Nothing carries into the build. It’s a thinking tool.

  • You still need a designer. We review every version and push back on crowded screens.

  • Watch what goes into prompts. We agree with the client up front what we share with Claude, and leave out anything confidential, such as unreleased features.

It works best early, when the big questions are which features exist and where they live. For a product with settled flows and a strict design system, small changes are quicker in Figma. That’s why we use it to start new app projects in our SaaS UI/UX design work.

Also read: Onboarding and empty states for AI tools, AI SaaS dashboard design examples, How to choose a UX design agency.

AI wireframing FAQs

1. Can Claude make app wireframes?

Yes. Ask Claude for a wireframe as an artifact and it builds a clickable prototype, where screens link to each other and forms move to their next state. Keep the styling plain, so the conversation stays on which features exist and how users move between them.

2. Does AI wireframing replace Figma?

Not for us. It replaced Figma wireframes only. High fidelity design still happens in Figma, and our designers start it from the flows the client locked in the artifact, so there's no wireframe stage to redraw.

3. Does it really mean fewer rounds of changes?

In our projects, yes, because the big flow changes come out while the client is still trying ideas, not weeks later.

4. How do you stop clients adding features forever?

We review each version before anything is locked, and a developer checks it. A feature that's costly to build gets a conversation about scope and budget, not an automatic yes.

About the author

Chandresh is an engineer at Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.

How we know this

The Draft, Send, Steer, Lock loop is our own process, not a published standard.

Design call

Want your app flows wireframed this way?

Send us your app idea or brief and we will show you how this loop would work on your main flow.