Yes, I see your point. Full story of what my issues are: This is for an update to my app. Currently my app is parsing a 700k text file and putting that into a database. This wasn't that big of a deal to me because my app still remains under 2MB on a users system and there are no issues in not being able to read a large text file, etc. I'm needing to update my app and here are the issues:
1) I have a 1.9MB text file that I need to read and spit into a database. This means that I will now have the 1.9MB text file (or files if I split) plus the storage for the database, thus almost doubling the footprint of my app. 2) Due to the higher footprint of my app, it is more likely to be purged by users who are scarce on space. 3) I could have the database already created and have the app download it from my server, however bandwidth costs money. Also, I'd probably gzip the database in this instance and still need to uncompress the database file when it gets plopped onto the SD card. 4) If I put the database on the SD card, I have to rely on the user a) having a SD card and b) the user not having a SD card full of Brittany Spears and other cruft. I guess these are just the growing pains of my app and these are things we are increasingly going to have to deal with. I've just been going back and forth amongst these options not really liking any of them. It seems like the growing advice on this list is to store the larger stuff on the SD card and have the user download it when the application first runs in order to maintain a smaller internal memory application footprint. If there are any other ways that I haven't thought about, I'm open to advice. And Mark, I do appreciate your comments. It sort of made me face the inevitable that I was trying to ignore :). Justin On Fri, Jan 29, 2010 at 8:04 AM, Mark Murphy <[email protected]>wrote: > > > So, after the > > application is installed on a users device, all contents remain > > compressed? > > Most do, yes. Some things get unpacked I think (e.g., the compiled > classes). > > > The reason I'm compressing the file to begin with is to stay under the > 1MB > > file file size limit for files in res/raw. Yeah, I could break things up > > into separate files, but that's sort of a pain to maintain. > > And trying to un-GZIP a stream isn't? :-) > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > Android App Developer Books: http://commonsware.com/books.html > > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
