Thanks for the info guys. I suppose the SD card approach is the way to go. It sounds a bit complicated but it makes more sense because my app doesn't really need the pics in memory, they are mostly just for occasional reference.
On Jan 27, 12:10 pm, TreKing <treking...@gmail.com> wrote: > On Wed, Jan 27, 2010 at 9:49 AM, ian <stilbit...@gmail.com> wrote: > > My almost compled app has a couple of hundred images and tips the > > scales at a (bloated) 11 mb. > > > But I'd rather leave it that size. > > Why? > > > So I'm trying to figure out what this would mean to a user. > > For me, personally, this would mean that unless your app was the most > awesomest thing ever on my phone and completely indispensable, it would be > the first to go when I needed to clear space for something new. And I would > probably never re-install it knowing how much space it took up. > > I'd second Mark's suggestion to cache to the SD what you need as you need > it. Will the user really need "a couple of hundred images" at any given > time? > > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered > deviceshttp://sites.google.com/site/rezmobileapps/treking -- 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
