You can push your app content updates via Trigger.io's servers for app sizes up to 250Mb. For larger content, or if you want to host content that is to be re-used in your web app or other apps, then you can Reload with a 3rd party CDN like Rackspace Cloud Files.
Read about the Reload module to enable it and learn about the concepts.
Once you have the module enabled you can push updates to your existing users through the Toolkit UI, command-line tools or standalone build API.
Use the Reload tab in the Toolkit to manage your streams and push updates
In this tab, you can manage your streams of users - this allows you to push different code to different users for A/B testing. By default there is a single stream which enables you to push to all users without any extra configuration.
You can also see your configurations here - how many unique users we have detected that are using your app built against which minor version of the Forge platform.
Once you have built and tested new code that you wish to deploy, you can click the 'Push to stream' link from this view in order to push the update.
Some of the functionality of reload can be accessed via the command line, which allows automation of certain tasks, such as pushing an update. The commands available are:
forge reload list: This will list all available streams for your app
forge reload create <streamname>: This will create a stream called
<streamname>which can then be pushed to.
forge reload push <streamname>: This will push the last build to
<streamname>, it is likely you will want to run
forge build reloaddirectly before this command in order to build your current
If you are building a content-heavy app including large images or videos it is recommended that you host the app content and Reload it from a CDN like Rackspace Cloud Files.
You must use a CDN with Reload if your app size is greater than 250Mb.
CDNs are optimized for download performance according to your users' locations. Hosting your app content on a CDN with Reload enables you to push large content files down to your app in the background, and link to the same content from your web app or other mobile apps.
Using Reload with a CDN enables you to overcome the challenges of large content in mobile apps. Your app must:
With Reload and a CDN you can have a small app hosted on the App Store or Google Play which downloads large content in the background.
When you push a Reload via a CDN the end-user experience is the same and you are able to use the same Reload APIs in your app code.
The process for pushing the Reload has some extra steps. You can see these steps in action with our screencast tutorial demonstrating Reload integrated with Rackspace Cloud Files.
The process is:
You can use the standalone build API to push a Reload hosted on a CDN in which case you must perform steps 2 and 4 manually at the command-line. You can find detailed instructions for those steps by clicking through the links against them above.
But the simplest way is to use the Toolkit UI which automates steps 1 and 4.
Currently, pushing a Reload update will cause iOS devices to copy files out of the installed app bundle into a secondary area. This is due to sandboxing rules which prevent us directly accessing files in your installed app after a Reload has been completed. In order to avoid your app taking too much storage space on the device, it's recommended you distribute larger files using something like forge.file.saveURL, rather than including them in the app bundle.
We are actively looking for a way to avoid this limitation.