Updating Published Apps

To update a live app, make changes in the editor, test them in preview, then publish a new version. Users receive the update after publishing completes.

Republishing Changes

The preview can show unpublished work, but the live app changes only when you publish again. Use Review and publish to confirm app details, visibility, and any changes before replacing the live version.

Publishing a small update usually takes a few seconds. Updates that change stored data can take longer because the platform may need to run a migration.

What Users Receive

Users automatically get the newest published version. If the app is paid, existing buyers also receive future updates at no additional cost.

Their data remains private and isolated during updates. A user's database belongs to that user, not to the app creator or other users.

Update Checklist

Before publishing an update:

• Test the app in preview, especially any new or changed flows.
• Check that forms, saved data, and empty states still work.
• For major data structure changes, consider smaller incremental updates.
• Stay on the publishing page until publishing and any migration finishes.

Troubleshooting

If users do not see the latest version, confirm that the update was published successfully. Refreshing the app can also help if a browser is holding on to an older page.

If publishing fails during a migration, simplify the change or publish the structural change in smaller steps. See Data Migrations for details.