Google Stitch: turn an app idea into screens you can work with

A booking app sounds straightforward until you start drawing it. Customers need to choose a service, find a free slot and understand whether the booking went through. Staff need a different view. A cancellation has to lead somewhere. Those decisions shape the interface before anyone connects a calendar or takes a payment.

Google Stitch gives that stage of a project its own workspace. You describe the experience, bring references and develop the screens on a design canvas. The appeal is being able to discuss an interface while you have something visible to react to.

Start with the job the screen needs to do

Google’s Stitch canvas accepts text, images and code as context. Its design agent works across the project, and an agent manager helps organise different directions.

For the booking app, a useful first brief could ask for a mobile service list, appointment selection and confirmation screen, with a separate daily schedule for staff. Include the constraints that matter: customers should see the price before choosing a time, and the confirmation should make the next step clear.

That gives you specific decisions to make when designs appear. Are the available times easy to scan? Can someone change the service without losing their place? Is the confirmation clear enough to prevent a second booking?

Try the flow between screens

Stitch can connect screens into clickable prototypes. That makes it possible to walk through a sequence and ask for changes to the journey. Its voice controls also support design discussions and requests for alternative layouts. Google’s design overview describes both features.

The May update added streamed design work that you can steer as it develops. For a project with several plausible layouts, this offers a way to explore alternatives before committing to one.

Keep the design rules with the project

A common problem appears after the first few screens: the buttons, spacing and colours start drifting. Stitch’s DESIGN.md format lets you import and export design rules between projects and tools. Google has also published its draft specification. The DESIGN.md announcement explains the format.

For the booking app, those rules could describe the purpose of the main action colour, the hierarchy of headings and the treatment of selected time slots. Recording those decisions gives later screens a clearer starting point.

Take the design into implementation

Google lists handoffs through AI Studio and Antigravity, plus web publishing through Netlify. Its current workflow announcement describes sharing a preview through AI Studio and exporting screens to Antigravity to connect backend logic.

For a booking product, that next stage includes the actual appointment records, availability rules, staff permissions and payment behaviour. Decide who will build those parts while you are still choosing the screens. A clear handoff saves the design from becoming a collection of attractive views with unresolved interactions.

Stitch looks most useful when you have an app idea whose interface still needs working out. Bring one complete user journey, explore a few directions and carry the chosen design rules into development. See the Google Stitch tool guide or open Stitch.