Goal: understand exactly what people will receive before making an app live.
Check the main journey: find a task, read its details, and perform the actions intended for that user. Try empty data, longer text, and a narrow screen. Inspect the access policy rather than relying on which buttons happen to be visible.
In the project, open Publish or Publish project. Review each check and use its link back to the relevant editor area if something needs attention.
When offered, choose a platform address and inspect its availability. Reserving an address, recording a release, and serving it publicly are related but distinct. Custom domains and independent frontend publishing are not part of the current frontend foundation.
The panel may offer Reserve address and publish or Publish this version. These record the selected app revision. In an environment with serving enabled, Make live selects the release people will use. A release marked recorded or in production is not necessarily reachable from the internet; read the panel's actual status.
If publishing or serving is unavailable, resolve the reported requirement with the operator. Do not use repeated clicks or another account to bypass a block.
When authorized to go live, open the supplied address and verify the intended signed-out and signed-in journeys. The production environment starts with its own data: sample preview records are not copied into it. App-user invitations and access are separate from your builder sign-in.
Next: Update a published app →