Publishing your app
Take the app from preview to live, with checks on the way.
Publishing is the moment your project becomes something other people can use. It is a deliberate action, and it can be reversed.
Preview and live are separate
While you build, changes land in the preview. Your live app does not move until you publish. Customers see the version you approved, not the version you are halfway through.
Publishing
Check the preview one last time, then publish. Before the app goes live, Automated QA and Security scanning can run their checks, and a serious problem can hold the publish until it is fixed. When the build finishes, the live app updates.
Before your first publish
- Confirm your email address if you have been asked to.
- Set a project name, icon and social preview image.
- Run through the main task as a real user, signed out and signed in.
- Check that no test keys or sample content are left in.
- Decide whether the app should be public or require sign-in.
The project address
A published project is reachable at an address you can share. For anything customer-facing, connect a domain you own. See Custom domains.
What publishing does not do
It does not change your data or send emails by itself. It deploys the app as it exists in the preview at that moment.
Next: Custom domains.
Was this page helpful?