Ben, I agree with you about the crying need. From a product roadmap point of view, this is a really obvious value for many developers. But I wouldn't jump to a solution too quickly. I've been thinking about the problem for a few days now and my opinion is that initial load data should come from an online web services source, not packaged in the assets. This allows developers the option of updating their database without releasing a new version of their app. And you have to remember that users will always have a network connection when they are installing from the Marketplace, so we should take advantage of that.
I'm going to investigate the option of using Amazon S3. There exists a Java library for S3 access along with methods to access all the AWS services: http://aws.amazon.com/sdkforjava/ The question remains, if I just use the S3 objects and methods in this library, will it pull in a big fat tail of unrelated code that I don't want weighing down my mobile app. -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
