We\'re building an API and mobile app on top of a database that has a few hundred thousand records in the main table of interest.
Our mobile developer is pushing hard ab
Although this is an old question, I have recently faced this several times and wanted to generalise the problem by writing a design pattern for this issue for any database (in my case sqlite on mobile devices and mySQL on the central Server) and any schema. Here is the design Pattern on google docs:
mobileSync on Google Docs
Also, there is an App and Unit tests to prove that the pattern works as specified. See GitHub Link:
IOS App for MobileSync
Or, search on github for johngoodstadt and then mobile Sync. The Android version is coming soon (May 2016).
It does not provide total sync services that paid for services would provide but if your requirements are typical of most mobile solutions it could save you much time in experimentation. Please feedback any issues errors,bugs so I can refine this designPattern/Code
Thanks
John Goodstadt