I've seen 3-4 different people ask some variation of this question in these forums. It seems like a very common question/need. I'd like to see this specific topic addressed in part of the Dev Guide, with various uses cases and proper solutions.
Pankaj, regarding your specific application: Approach 2 sounds more sensible because the application is decoupled from the data. You could change the data without affecting the application, and vice versa. You could even take this modular approach a step further and allow installation of pluggable, multiple databases. For example, maybe db1 has Bible verses, db2 has Chinese fortunes, db3 has funny movie quotes, etc. People could choose to install only the database(s) that they care about. (With approach 1, you would have to include all databases in the apk file, which could become cumbersome.) My two cents. :) -- PJ On Oct 29, 1:34 am, "Pankaj Godbole [Andruid]" <panka...@gmail.com> wrote: > Here is some background about my app: > > I am developing an Android app that will display a random quote or > verse to the user. For this I am using an SQLite database. The size of > the DB would be approximately 5K to 10K records, possibly increasing > to upto 1M in later versions as new quotes and verses are added. Thus > the user would need to update the DB as and when newer versions are of > the app or DB are released. > > After reading through some forums online, there seem to be two > feasible ways I could provide the DB: > 1. Bundle it along with the .APK file of the app, or > 2. Upload it to my app's website from where users will have to > download it > > I want to know which method would be better (if there is yet another > approach other than these, please do let me know). > > After pondering this problem for some time, I have these thoughts > regarding the above approaches: > > Approach 1: > Users will obtain the DB along with the app, and won't have to > download it separately. Installation would thereby be easier. But, > users will have to reinstall the app every time there is a new version > of the DB. Also, if the DB is large, it will make the installable too > cumbersome. > > Approach 2: > Users will have to download the full DB from the website (although I > can provide a small, sample version of the DB via Approach 1). But, > the installer will be simpler and smaller in size. Also, I would be > able to provide future versions of the DB easily for those who might > not want newer versions of the app. > > Could you please tell me from a technical and an administrative > standpoint which approach would be the better one and why? > > If there is a third or fourth approach better than either of these, > please let me know. > > Thank you! > > Pankaj Godbole > Andruid -- 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
