Project type
Choose a mobile project deliberately
Mobile work starts before the first prompt.
Pick `Mobile app` when the product should be a Flutter app
Flutty maps that choice to a Flutter project with mobile-oriented runtime and preview behavior.
Pick `Website` when browser publish is the target
Website projects use the normal browser preview and website publish flow.
Keep the product type stable after creation
A mobile project and a website project can share the same chat workflow, but their preview and release surfaces are different.
Preview
Preview on a device surface
Mobile projects do not rely only on the `Website` tab mental model.
Use the mobile preview surface for app behavior
The embedded device view is where touch, phone layout, and mobile startup behavior are easiest to check.
Open the standalone iPhone preview for focused testing
It keeps the preview large while still linking back to the project.
Use the web preview only as a secondary check
Flutter mobile projects can expose web output, but that does not replace device validation.
Go Live
Prepare Mobile Go Live before launch
Mobile release setup is more credential-heavy than website publish, so treat it as its own checklist.
- 01
Connect GitHub first
The release path needs a repository connection so the build service can work from a stable project source.
- 02
Save app identity and store metadata
Review display name, bundle or package identifiers, release channel, release notes, and store defaults before launching.
- 03
Add only required secrets
App Store Connect, Google Play, signing, provisioning, and keystore inputs are stored through the mobile release setup instead of chat text.
- 04
Draft the setup prompt when the agent should prepare files
The Go Live panel can place a precise mobile setup prompt into chat instead of asking you to remember the tool sequence.
Status
Track the release run
Launching a mobile release starts an asynchronous release run.
Expect a queued run, not an instant store result
Flutty tracks the latest release batch while the worker starts the build.
Use the build link for low-level build details
When a Codemagic build exists, the release panel links to it directly.
Treat missing setup as actionable
If Flutty asks for a bundle ID, App Store credential, Google Play service account, or signing file, complete that setup before launching again.