It's essentially the same, but you do have the option, if the iOS device is to serve as a client of a solution hosted from FileMaker Server to only put the front end file on the iOS device. I haven't tried that to see how well it works, but in theory, it should be possible.
that method works very well (I have a client that does this). however you have the same possible 'disconnects' as with fully-hosted solutions.
all-on-iOS would be limited by storage/memory, but multiple files (data separated) would work.
the advantages (with data hosted or not) of the interface is the ability to quickly swap changes as long as it's interface changes and not schema changes. research data separation elsewhere for the good, the bad regardless of platform.
then also research sync methods whether the data is separated or not.
The solution will be entirely on the iPad. I have used DS on desktop before - just not on iOS.
1 of 1 people found this helpful
You might consider not using the Data Separation Model, if the database is only going to be on the iPad. I would use the ios SDK and then use the update process like the one at this link http://www.yzysoft.com/filemaker-tips/how-to-update-native-ios-app-created-with-filemaker-ios-app-sdk/