Auto-save
The builder auto-saves your configuration 3 seconds after you stop making changes. A Saved indicator appears in the top bar when the save completes. While a save is in progress, the indicator shows Saving.... If you close the tab before auto-save finishes, a browser dialog warns you that unsaved changes will be lost.
You can save manually at any time with ⌘S on Mac or Ctrl+S on Windows and Linux. Saving manually also updates the version history timestamp (see below).
Config changes vs rebuilds
Not every change requires a new app binary. Most builder changes are config-only: they are fetched by the app on next launch and apply without any App Store or Play Store update. A smaller set of changes require a full rebuild because they affect data that is compiled into the binary itself.
| Change | Rebuild required? | Takes effect |
|---|---|---|
| Brand color | No | Immediately on next app launch |
| Accent color | No | Immediately on next app launch |
| Font family | Yes | After rebuild and app store update |
| Block add / remove / reorder | No | Immediately on next app launch |
| Block content (headline, image, collection) | No | Immediately on next app launch |
| App name | Yes | After rebuild and app store update |
| App icon | Yes | After rebuild and app store update |
| Splash screen | Yes | After rebuild and app store update |
| Bundle ID / Package name | Yes (and re-submission required) | After rebuild and app store update |
| Shopify store URL | Yes | After rebuild |
Config-only changes are applied the next time a user opens the app. On launch, the app fetches the latest config from Appolar's CDN. There is no manual publish step and no cache-busting delay — users on the latest app version see the updated layout or colors on their very next launch.
Note. When you make a rebuild-required change, the builder flags it with a banner and queues the rebuild once you confirm. Config-only changes save silently with no prompt.
Version history
The builder keeps the last 10 saved configurations. To view them, go to Builder > Settings > Config history. Each version shows a timestamp and a plain-language summary of what changed relative to the previous version — for example, "Brand color changed from #1A1A1A to #0057FF" or "Hero banner block removed from Home screen."
To restore a previous version, click it in the list and select Restore this version. The restored config becomes your current working config and appears in the preview immediately. Restoring does not automatically trigger a rebuild — it simply replaces your current config. Review the restored state in the preview and trigger a rebuild manually if the restored version includes any rebuild-required changes.
Version history is per-merchant and is not shared across accounts. If you have multiple team members with builder access, each save — from any team member — counts toward the 10-version limit.