App Versions and Publishing

Before any app that is created on the builder is ready to use, it has to be published.
The “Publish App” button is present on the top right corner when you have opened an app on builder.axonator.com.
Every time you modify an existing form or create a new form and save it, you must publish the app in order for your changes to be reflected across all other devices (including the mobile app).

• The first time you publish any app is termed as a Major Publish (which creates app version 1.000).
• Every subsequent publish after that is termed a Minor Publish.
• Every minor publish increments the version number by a factor of 0.001.
• Example – You publish the app initially (v 1.000 created), then make some changes to a form and publish again (v 1.001 is created) 

Publish for Test –

The publish for test option lets a user publish an application for testing purposes.
This lets the user submit data via forms to test if the app built is working as expected. 

Once the user has tested the app thoroughly, they need to re-publish the app before it is ready to be used by a wider audience as a final product. 

Upon re-publishing, the data submissions that are recorded during the testing phase will be erased.
Before publishing an app, a user must –

• Ensure there are no draft forms, workflows, report or email templates. Everything must be saved before you can successfully publish an app version. 
• Have a stable internet connection. App publishing cannot take place offline and one must ensure their internet connection is stable enough for the short span of time it takes for the app to be published. 

Once a version is published it cannot be reverted. Therefore it is critical to ensure that all changes made are done correctly. One can always publish a new version any time but it is good practice to ensure all changes are in order before publishing a new version. 

There is no limit to the number of times you can publish a new version of an app.