Build apps

Draft, publish and history

Changing a live app shouldn't break it for the people using it. In appTown, every change goes into a draft first.

#The draft

Everything you change in the builder goes into the draft. You and other builders see the draft in the preview; people using the app keep seeing the published version until you publish.

#History

Every change is saved automatically as a numbered change (#1, #2, …) with who made it and when. Build → History lists them all; changes the AI made are marked "AI:".

• Undo takes back one unpublished change. If later changes depend on it, appTown says so instead of undoing.
• Undo all throws the draft away and goes back to the published version.
• Restore copies an earlier state into the draft as a new change, so you can undo that too.

#Publish

Publish makes the draft live as the next version (v1, v2, …), with optional notes. If automations have saved tests, publishing runs them first and warns you about failures (it doesn't stop the publish).

#Roll back

Roll back publishes an earlier version again as a new version, for example after a mistake. The draft goes back to it too.

#Records are never touched

Publishing, undoing, restoring and rolling back change the app's design, never its records. Fields and tables you removed keep their data; see Tables and fields.