Yes, we are doing this all the time. Not only for the first installation, but also when updating the solutions with new versions.
Wwhen updating we will first backup data, then upgrade version of files and then restore data.
We ended up building a model and a set of routines, our mobile framework, that we keep improving.
if you have questions, please ask and if I can not answer, I will get help from my team.
please also have a look here:
Am I correct in my suggestion, would this be the simplest way? Using technique #1 or #2???
It makes sense to me to have a "utility" filemaker file which would run all the scripts to install, update etc... right? Then if this is the case, is the filemaker file pulling files from a host via a container?
I'm thinking that if this is the correct (and simplest) path to follow, I might start building an iOS "Installer" to become as generic as possible, but I suppose I don't want to re-invent to wheel either.
A utility file would be what I use. Easier to check for updates.
mattman has a decent example of how he does this on his ISO site. I am assuming by standalone you mean the data will only ever be local to the iOS device. This means the data file only needs to be downloaded once and the updates will be for the UI files.
For the installer you can have a web clip profile that gets emailed and that grabs everything and also provides for another web clip profile that will launch the solution.