What should you ask Stitch to design first?
Describe the person, their task and what they need to learn after the action. Start with one flow so you can judge the design before generating more screens.
For a neighborhood tool-lending app, ask for a phone-sized page where a borrower can request to keep a drill until Thursday. Show that it is currently due Tuesday. Ask for one clear action and a separate state for a requested date that has been taken.
Google documents starting from text and bringing images, text or code into the canvas as context. You can also iterate with voice. For a first draft, use your own reference assets and invented information so the work can be reviewed without exposing customer data.
What does the Stitch prototype help you find out?
Connect the screens and use Play to try the path. Check whether someone can find the next action and tell which date applies when they finish.
Google documents generating the next screen from a click. Check any automatically added step against the rule you meant to show. If the prototype jumps to “Thursday confirmed” when there is no space, add the unavailable-date outcome before asking for feedback.
Give someone a task and watch the first action they try. If they need you to explain how to start or which date applies at the end, change that part before generating another layout.
What can you take from Stitch into another tool?
Decide whether the next person needs the screens, the shared visual rules or a starting point they can run and change. Save the relevant output before you rely on a connection.
Google’s original announcement described Figma and HTML/CSS exports. Export choices can change with the project workflow. Check the exact output you can open before planning your handoff around a particular format.
| What the next step needs | What to keep |
|---|---|
| Design rules | Export DESIGN.md for rules such as type and color. Keep the sample screens and behavior notes with it. |
| A starting point for code | Google documents exporting screens to Antigravity. Open one transferred screen and check whether it fits the app you already have. |
| A link people can open | Google describes sharing through AI Studio and a separate Netlify publishing option. Check what each link shows and who can open it. |
What should you check before relying on a Stitch result?
Check the generation allowance you see in your account. If you publish a design, budget separately for whatever hosts it or stores real records.
In a private test copy of the running app, try saving a made-up extension and reload the page to check the result. If the date has already been taken, make sure the old date stays saved. The prototype helped you decide how to explain those outcomes. The running app is where you verify they happen.