Tutorial - Updating an appMobi Application to a New Version of the appMobi API
v1.01 : 05.05.2011
The purpose of this document is to show developers how they may take an existing application and update it to take advantage of the newest appMobi API.
Ultimately, the decision of whether or not to create a new release belongs to the developer. If there is a bug fix or new API command that is important to incorporate into an application, creating a new release will allow you to take advantage of that new functionality. However, given the requirement of creating and resubmitting a new app build for your new release, it may not always be justifiable to do so. To make an informed decision, it's important to understand the appMobi XDK iteration naming convention.
The appMobi version number is organized into three-tiers. Any changes to the version number indicates the release of a new version of the appMobi API and an associated XDK.
When new versions of the appMobi XDK become available, the XDK will notify developers by the presence of the update prompt ( ). The "add new release" button ( ) is activated only when the current application project is out of sync with the installed version of appMobi. Pressing it initiates an optional process that makes a copy of your app project and binds it to the installed version of the XDK.
Any time that a new release is created, a new compile build ( ) process will be required. Developers with a live application in the App Store and/or Android Market, must replace the previous version of the application through resubmission.