Google Stitch Tutorial: Design an App UI with AI

This Google Stitch tutorial shows you how to go from one sentence to a full mobile app design, then to Figma, then to a real Next.js and Tailwind page. Stitch is a free AI design tool from Google Labs: you describe an app, it designs the screens and gives you the front-end code with them.…

The YouTube player loads only when you press play. Open on YouTube

This Google Stitch tutorial shows you how to go from one sentence to a full mobile app design, then to Figma, then to a real Next.js and Tailwind page. Stitch is a free AI design tool from Google Labs: you describe an app, it designs the screens and gives you the front-end code with them.

Watch the video: https://youtu.be/CE2nEiv92Qs

If you build apps like I do, you know the moment: the backend is ready, and the design is a blank screen. Stitch won’t replace a designer, but it gets you to about seventy percent in ten minutes. By the end of this post you’ll know how to write a good Stitch prompt, how to edit without wasting your free limit, how to hand the design to Figma or to your code, and the four things you still have to fix by hand.

What you need

  • A Google account. You must be 18 or older.
  • A browser. Nothing to install.
  • A country where Gemini is available. Stitch’s interface is English only, but it’s available in the countries where Gemini is, which includes Saudi Arabia and most of the Middle East. Check Google’s list for your country first.

Stitch is free. There’s no paid plan, and I cover the usage limits further down.

Step 1: Design an app from one prompt

Go to stitch.withgoogle.com and sign in with your Google account.

  1. Pick App for a mobile design, or Web for a website. Today we’re designing a mobile app.
  2. Pick the model. There’s a fast mode and a Pro mode that thinks longer. Start with the fast one: it’s quicker, and it’s the one that can copy your design to Figma later.
  3. Write the prompt like a brief for a designer.

Here’s the prompt I used for a small help desk app:

A mobile help desk app called FixIt Desk, for a small IT team.
Three screens: a home screen with open tickets and their priority,
a new ticket form, and a ticket detail screen with a chat thread.
Clean and friendly, teal and white, rounded cards, and big buttons.

In about a minute, three screens appear on the canvas: a ticket list with priority labels, a form with a category and a description, and a chat between the user and IT.

My tip: name the screens you want. If you only write “a help desk app”, Stitch guesses the screens, and you spend your free generations fixing its guesses. A good Stitch prompt has four parts: what the app is and who it’s for, the exact screens, what goes on each screen, and the look (colours, shapes, mood).

Step 2: Edit screen by screen

Click a screen to select it, then type the change. For the home screen I asked:

Add filter chips at the top: All, High, and Mine.

Then, in a second prompt:

Move the new ticket button to a round button, bottom right.

Stitch changes the selected screen and leaves the other two alone.

My rule: one change per prompt. When I ask for five changes at once, it usually gets three right, and I pay for the redo with my limit.

Three more things worth knowing:

  • Theme settings, not prompts, for colours and shapes. Open the theme settings to change the accent colour, the corner radius or switch to dark mode, and every screen updates together.
  • Variants. Not sure about a screen? Ask for variants, compare them side by side, and keep the one you like.
  • Prototypes. Stitch can link your screens into a clickable prototype: tap a ticket and the detail screen opens. It’s great for showing a client the flow before you write any code.

Step 3: Export to Figma

Select your screens and open the Export menu. You’ll see options like Copy to Figma, Download, copy code, and links to Google’s own developer tools.

  1. Click Copy to Figma.
  2. Open Figma, any design file, and paste with Ctrl+V (Cmd+V on a Mac).

Your screens land as real Figma frames, not flat pictures: layers you can select, with auto layout, so a designer can change a text or a colour in seconds. This is how I hand a Stitch design to a real designer: Stitch gets me most of the way, and a human makes it ours.

Stitch can also export your design rules as a DESIGN.md file: colours, fonts and spacing in plain text, so a coding agent can follow the same style.

Step 4: Turn it into a Next.js and Tailwind page

In the Export menu, choose Download. You get a zip with the HTML of each screen, a screenshot, and the design file. The HTML is plain HTML with Tailwind classes; it loads Tailwind from a CDN and keeps its own colours in a small config.

In my Next.js project I created a tickets page (app/tickets/page.tsx) and pasted the body in. Then three quick fixes:

1. JSX syntax. class becomes className, and tags like img and input close themselves.

2. Move the colours into your theme. Copy Stitch’s colours into your Tailwind theme so the CDN script can go. With Tailwind v4 that’s a few lines in your global CSS:

@import "tailwindcss";

@theme {
  --color-primary: #0f9d8a;
  --color-surface: #f4fbfa;
}

3. One component instead of five copies. The ticket card repeats five times in the HTML, so make it one component and map over your data:

type Ticket = { id: number; title: string; priority: "High" | "Medium" | "Low"; owner: string };

const tickets: Ticket[] = [
  { id: 1042, title: "VPN won't connect", priority: "High", owner: "Abd Almouhimen Shamout" },
  { id: 1041, title: "Outlook keeps asking for a password", priority: "Medium", owner: "Abd Almouhimen Shamout" },
];

function TicketCard({ ticket }: { ticket: Ticket }) {
  return (
    <li className="rounded-2xl bg-white p-4 shadow-sm">
      <p className="text-sm text-gray-600">#{ticket.id} · {ticket.owner}</p>
      <h2 className="font-semibold">{ticket.title}</h2>
      <span className="mt-2 inline-block rounded-full bg-primary/10 px-3 py-1 text-sm text-primary">
        {ticket.priority}
      </span>
    </li>
  );
}

export default function TicketsPage() {
  return (
    <ul className="space-y-3 p-4">
      {tickets.map((t) => <TicketCard key={t.id} ticket={t} />)}
    </ul>
  );
}

Run npm run dev, and the same home screen is now a real page. Swap the tickets array for a fetch to your API (mine is a Laravel API, see my Laravel API tutorial) and it’s live data.

Using a coding agent? Stitch also has an official MCP server. Connect it to Claude Code or Google Antigravity, and the agent reads your design and builds the page for you. I covered Antigravity in my Google Antigravity tutorial.

4 things Stitch still gets wrong

1. Copy to Figma is missing. That happens in Pro mode. Switch to the fast mode and generate again, or download the zip and import the HTML into Figma with an HTML-to-Figma plugin.

2. The content is fake. Made-up names, random stock photos and icons loaded from the web. Before you ship, swap in your real data and your own icon set (and host the images yourself).

3. Accessibility. Light grey text on white, small tap targets, and divs that act like buttons but aren’t real buttons. Check the contrast, make every tap target at least 44 pixels, and use real <button> and <label> tags.

4. Right to left (Arabic). Stitch itself is in English, but you can write your prompt in Arabic, or ask for an Arabic, right-to-left layout. Google doesn’t officially promise RTL support, so check the code:

<html lang="ar" dir="rtl">
  • Swap left/right margins and padding (ml-, mr-, pl-, pr-) for logical start/end classes (ms-, me-, ps-, pe-).
  • Pick a real Arabic font, for example with next/font/google.

Then the whole screen flips the right way.

Free limits: what most people learn the hard way

Stitch is free. There’s no paid plan, and you can’t buy more generations. You get a usage limit that resets on its own, and Google has changed the numbers (and the names of the modes) more than once, so check the counter in your own account.

The hard way part: every edit and every variant counts, and Pro mode uses the limit up faster. So plan your screens before the first prompt. I write mine on paper first, and I rarely hit the limit.

Quick checklist

  • [ ] Prompt written like a brief, with every screen named
  • [ ] Fast mode if you need Copy to Figma
  • [ ] One screen and one change per edit prompt
  • [ ] Colours, corners and dark mode set in the theme settings
  • [ ] class → className, self-closing tags, colours moved into the Tailwind theme
  • [ ] Repeated cards turned into one component
  • [ ] Real data, own icons, contrast and 44 px tap targets checked
  • [ ] For Arabic: dir="rtl", start/end classes, Arabic font

FAQ

Is Google Stitch free?

Yes. Stitch is a free Google Labs tool with a usage limit that resets on its own. There’s no paid plan and you can’t buy extra generations.

Is Google Stitch available in Saudi Arabia?

Yes. Stitch is available in the countries where Gemini is available, which includes Saudi Arabia and most of the Middle East. You need a Google account and must be 18 or older.

Does Google Stitch support Arabic?

The Stitch interface is English only, but you can write your prompt in Arabic or ask for an Arabic right-to-left layout. Google doesn’t officially promise RTL support, so check the code for dir="rtl", logical start/end classes and an Arabic font.

Why is Copy to Figma missing in Stitch?

Copy to Figma works in the fast mode. If you generated in Pro mode, generate again in the fast mode, or download the zip and import the HTML with a Figma plugin.

Can I use the Stitch code in production?

Treat it as a strong first draft. Convert it to components, move the colours into your own theme, replace the fake content, and check accessibility before you ship.

Keep learning

Watch the video: https://youtu.be/CE2nEiv92Qs

Which app would you design first? And which topic do you want a video about next? Tell me in the comments on YouTube.

Tools I use

🎙 Voice-over made with ElevenLabs: https://try.elevenlabs.io/p825ulh2ac98
Some links are affiliate links; I may earn a commission at no extra cost to you.

Sources

  • Google Stitch: https://stitch.withgoogle.com
  • Google, Stitch announcements on blog.google and the Google Developers Blog (export to Figma, code export, DESIGN.md, MCP server).
  • Google AI Developers Forum, Stitch staff answers on access, availability and usage limits: https://discuss.ai.google.dev/
  • Tailwind CSS, theme variables: https://tailwindcss.com/docs/theme

Leave a Reply

Your email address will not be published. Required fields are marked *