Publishing an app

Publishing fixes an app's pages, definitions, and actions. New memory keeps flowing through the published version.

Publishing an app for the first time

A published app is billed, so its first publication needs an Owner or Admin.

• An Owner or Admin can publish any app directly.
• A steward who is not an Owner or Admin submits one revision for approval, with an optional note.

A submission works like this:

1. The steward submits a specific revision.
2. Owners and Admins see it under Waiting for approval and get an in-app notice.
3. An Owner or Admin approves or rejects it. A rejection carries a reason.

Approval publishes exactly the revision that was submitted. Later drafts do not change what the reviewer approves.

One submission can be pending for each app. Submitting a newer revision replaces it, and the steward can withdraw it. If the submission was replaced or withdrawn before the review, the approval fails and nothing changes.

Publishing fails if:

• the specification is not valid;
• any definition is unconfirmed; or
• a source the app reads is not connected.

Publishing also fails if someone else published first. Reload and publish again.

Later releases

Once an app is published, a new release does not change the bill. The steward, an Owner, or an Admin publishes it directly, with no approval.