Preview
Treat preview as the default check
Use browser preview often while the change context is still fresh. For mobile app projects, use the mobile device preview and Go Live page instead.
Validate the route you actually care about
The route field lets you inspect `/`, nested routes, or any current page path without leaving the workspace.
Use refresh when the current route is stale
Reloading the route is the fast path when the preview exists but the page needs to be re-checked.
Use `Open in new tab` when the embedded preview cannot tell the full story
This is especially useful for access edge cases or browser behavior that is easier to inspect outside the iframe.
Expect explicit fallback states
If the preview is still generating, waiting for access, or timing out, Flutty shows that state instead of pretending the site is ready.
Keep mobile checks separate
A Flutter mobile project may expose web output, but store readiness depends on the mobile preview and Go Live setup.
Recovery
Wake preview deliberately when the runtime is cold
A missing preview does not always mean the project is broken.
Use `Start preview` first when the runtime is sleeping or unavailable
The generate header exposes this as a quick wake-up action.
Wait for workspace preparation before judging the result
`Website` depends on runtime availability more directly than `Database` or the documentation links do.
Retry the same route after wake-up
This keeps the validation focused on whether the runtime came back, not on a different page.
Publish
Follow the publish sequence in order
Website publishing is cleaner when you treat it as a release sequence instead of a blind final click.
- 01
Confirm the preview state first
The current `Website` tab should already match the direction you want to ship.
- 02
Make sure the project has a deployable snapshot
Flutty publishes from a state it can promote, not from any arbitrary intermediate moment.
- 03
Open the publish flow and review the target details
If the project is already live, treat this as an update to the existing site rather than a brand-new release.
- 04
Publish only after the workspace is stable
If you still expect more structural prompts, stay in preview mode longer.
Details
Review the publish details before going live
The website publish flow is more than a single button. It also controls the public identity of the site.
Website name
Use a clear public-facing name for the published project.
Slug and live URL
Review the slug carefully because it affects the live site address.
Icon generation or upload
Flutty supports generating a publish icon or uploading one, so the published site does not need a placeholder identity.
Update path for existing sites
If the project has already been published, the same flow is used to push the next live version.