Have you considered just making the application come without data and then pull the data from a server? It would be much easier on you to not have to republish the application every time you wanted to change some of that data.
The basic steps would be something like this: 1. Publish app without data 2. App checks for the last time it got data against the last update on the server 3. Download updated data if needed You could have it check in the background each time the user used the application and notify them that they needed an update or use C2DM for push notifications. Steven Studio LFP http://www.studio-lfp.com On Monday, October 24, 2011 8:32:48 AM UTC-5, Todilo wrote: > > Hi, sorry for a bad subject name, just couldn't name it in a good way. > I have an application which is basicly like a wiki which presents > information and images. This information will change frequently (and > images) as well so I was wondering the best way to set it up. It > basically is a list of units and their statistics for a game. Since > unit information and statistics will change after each patch I need to > send that information out with an updated version of the app. What is > a good way of storing this information? Can I have a database which I > recreate upon every update(user will not change the data himself) or > is it better to just have .txt/xml files describing unit information? > > Ideas? Been away from android programming for some time. -- 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
