2 ms·
> mainly because on Android the SQLite wrapper is so clunky Go straight for a ContentProvider, even if you are not sharing access to the data in SQLite. That m
by Zigurd 12y ago
> mainly because on Android the SQLite wrapper is so clunky
Go straight for a ContentProvider, even if you are not sharing access to the data in SQLite. That makes it easier to build an observer pattern in Android. You can then build a SyncAdapter on the "back side" of this ContentProvider. Et voila, a synch'ed app.