Documentation
Generating a mobile app
From a description to an Android or iOS app project.
The mobile app builder works like the website generator — describe the app, get a first version, refine it in chat — with one extra decision up front: the platform.
Choosing a platform
Pick Android or iOS in the composer before you send the prompt. It changes the conventions the app is built to: navigation patterns, controls and layout differ between the two, and an app that ignores the platform it runs on feels wrong to the people using it.
Not sure? Android is the wider audience in most markets and the cheaper store to publish on. Start there.
Describing the app
Apps are defined by what people do in them, so describe actions rather than pages:
A habit tracker. People add habits, tick them off daily, and see a
streak for each one. A home screen with today's habits, a screen for
adding and editing them, and a stats screen showing the last month.
Reminders in the evening.The type chips — booking, e-commerce, fitness, social and so on — prefill a description for a common app shape. Edit it before sending.
Refining in chat
Sending creates the project and opens its chat, which stays available for as long as the project exists. Ask for screens, flows and behaviour: "add a settings screen with notification times", "the streak should reset if a day is missed", "move stats into the bottom tab bar".
Content inside the app
Apps read from the same kind of collections websites do — blog posts, products, courses, events and listings, managed in the sidebar rather than in the builder. Adding a product updates the app; you do not rebuild a screen. See content collections.
When the app itself is right, move on to settings, branding and stores.
Was this page helpful?