This is good and along the lines of one of my thought trails, but how does the device initially know where to make the web service call to get the config?
On Aug 3, 9:03 am, Matty <[email protected]> wrote: > If you have web services already, won't it be easy to add one that > allows clients to say "where should I look for content"? They could > send version numbers, their own phone number, or other information so > you can decide where to point them. Then the client could store that > information in a DB, or on the sdcard, or in memory... > > On Aug 3, 8:42 am, TreKing <[email protected]> wrote: > > > On Mon, Aug 2, 2010 at 9:28 AM, droidbm <[email protected]> wrote: > > > *Raw Resource: If I unzip the apk and change the settings file, it > > > becomes > > > invalid as I need to resign the apk. > > > Why are you unzipping the APK to change the settings file? > > You can have several raw resources, one for each configuration, and on first > > run read the one that's appropriate and use it to set up your app, applying > > the settings to, say, a SharedPreferences object. Done. What's the problem? > > > ------------------------------------------------------------------------------------------------- > > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > > transit tracking app for Android-powered devices -- 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
