Start with one complete journey.

Choose an outcome, not a collection of screens

A fitness app can have a dashboard, a workout library, a calendar and a profile before anyone can record a single workout. A smaller first version lets someone choose a session, complete it and see the result. That is a whole journey you can put in front of a person.

Write the first version as one sentence: a person can do this, and then this happens. Keep the result specific enough to test. That sentence is also the best brief you can give Sanic AI.

Build the flow before the polish

Create the pages the journey needs, then build their structure from components. Start with a readable heading, one clear main action and the information someone needs to decide. Link colours and fonts to your theme once those choices feel right, so later changes stay cheap.

Wire the actions early. A button that takes someone to the next page tells you more about the experience than several carefully styled screens with no working navigation. Reach for code when a step needs logic the built-in actions do not cover.

• Give the main action an explicit label, such as Start workout.
• Make it obvious what happened after an action succeeds.
• Provide a way back from every detail or result page.
• Decide what shows when there is nothing yet, or when a request fails.

Give Sanic AI a bounded brief

Ask for the complete small journey rather than the whole product. Name the pages, the actions and anything that needs to be remembered between screens. Say whether to use your theme, and which assets in the project to use.

If the journey needs a service, connect it first in Connectors and check it. Connecting makes the service available to your code and to Sanic AI; it does not create your tables, permissions or business rules.

Try the journey before adding more

Open Preview and follow the journey as a person would, not as its maker. Repeat it with missing information, on a different screen size and with an unexpected tap. The canvas is for arranging; the preview is where the journey either holds or does not.

Then take it to a phone. Touch targets, the keyboard and safe areas change how the same flow feels. Only when the small journey holds up is it time to add the second one.