There is a lot of FUD about Android fragmenation. The vast majority of the issue mentioned can be dealt with with properly following the guidelines, but there is one issue that I don't know how to deal with:
This forgotten issue is the SQLite versioning problem. For example, if the user moves to a phone with an older version of Android, I can support that older version of the platform just fine, but the user is Sh*t-out-of-Luck trying to move their database over and they cannot open their newer SQLite database on an older version of SQLite. What makes it even worse is that Cyogenmod uses a substantially newer version of SQLite, so when the user upgrades their crappy old phone to the shiny new model without Cyogenmod, they can no longer access their data. This is not a theoratical problem, I've had to deal with this issue a number of times. There is no solution other than: a) Package your own well-known SQLite version with your app. Is this even possible? b) Provide a custom data migration mechanism that exports your SQLite data and then imports it. While this might be trivial for a small app, it's a nighmare for an app like mine with a very complex database. Has anybody come across this problem and have any good ideas for dealing with this? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
