Another argument against including the database in the APK is that you save a considerable amount of storage memory. On some devices internal storage is very small - to the point where users have to remove one application to install another one - and if you include the database in the APK you actually end up wasting the space twice (since you cannot write to the APK and have to create a working copy of the database). Remember that not all Android devices can install APKs to external storage.
What you could do is include only a fraction of the data in the APK, a sort of teaser, and then let the user update the database when needed. On Monday, August 20, 2012 9:57:19 PM UTC-4, saernz wrote: > > Ohh genius! > > I never knew this service existed. This will help greatly and save me some > money as well! > Also it saves me having to fully implement and test my download code. > > Thanks for that! > > Cool looks like you can even set up test accounts for > application licensing which it uses > to provide the download URL. > > I guess if I wanted to release onto different markets I could create > a separate APK, I guess > I'll have to see how far the app goes first and if extending onto other > markets is worth it. > > On Tuesday, August 21, 2012 1:04:47 PM UTC+12, Nikolay Elenkov wrote: >> >> On Mon, Aug 20, 2012 at 8:08 AM, saernz <sae...@gmail.com> wrote: >> > Hiya! >> > >> > I'm creating an app which requires a large database to work (about >> 15mb). I >> > have decided >> > to not include it in the apk because I think some people might dislike >> > having such a big file stored >> > on their phone memory, and have instead decided to have my application >> > download the database on first >> > use and to store it on the SD Card. >> > >> > I guess I have two questions: >> > 1) Is it a good idea in this situation to separate the database from >> the >> > main apk package and host it else where, or is it completely possible >> to >> > include such a large file in the apk package? >> > >> > 2) If I end up requiring the user to download the database on first >> run, >> > where would the best place be to host the file? I've been considering >> google >> > drive and maybe dropbox, but I'm concerned mainly >> > with the amount of bandwidth that is allowed each day >> ... >> >> You can have Google Play host it for you at no additional cost: >> >> http://developer.android.com/guide/google/play/expansion-files.html >> >> They also handle authentication, integrity checking, etc. >> >> The downside is that you cannot use the same APK on other app >> markets, since this depends on your Google Play account, etc. >> > -- 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
