Background: I'm developing an app which comes with a rather large database (static, readonly), about 1.5Mb gziped. This database is then served from a content provider. The database has to be upgraded about 4 times a year. At first I thought about syncing/incremental updates (then it would be readwrite of course) but now I'm trying to keep is simple and thinking I should maybe just publish a new version of app when an update is needed and swap the database under the content provider...
Question: Since this is a content provider that is "public" and also might be serving other apps in the future... What is androids procedure for updating an app (via the market i.e). I'm assuming any currently running instance is killed overwritten and restarted if necessary but I have been unable to confirm this. Has anyone done something similar, hot swapping etc? --Albin -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
