I would go for a). Here are my reasons To retrieve your XML data to obtain server information is a fast TCP call. You can store the data in shared preferences. If the server versions are changing frequently within a day, query for the server data more often.
I think a data base (option b) might be an overkill if you have only a few version information to handle. Accessing the server information with shared preferences is straight forward. If the information is much more complex and is also handled on server side in DB, you might want to reconsider your evaluation and create a DB within your main app. In general a separate application which you have to manage adds complexity. You have to think about the following - how do you manage installation/uninstallation of your application? - when is the main application usable (when the second app is installed and has updated server information)? - is it required for your application to have always updated server information? - when a user manually uninstalls your second application (the app which communicates to the server), what do you do? These are only some basic questions. For sure you will come up with much more questions if you go with option b) or c). -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Sep 14, 1:56 pm, Neilz <[email protected]> wrote: > Hello. I'm wondering about the best way for android (on a mobile > device) to handle the equivalent of a web-app. Let's say a client > wants a version of their website (which contains server side > capability - database, a framework like struts/spring, ajax calls etc) > on a mobile device. How would you go about putting something similar > onto an android mobile? What are the options, and the technologies you > could use? > > Would you a) simply make a new front end sitting on the existing web > servers, written using a simplified XML which android can display > appropriately? So all you had to do was call the appropriate web > address to view the android version of the website. > > Or b) would you write a new app entirely for the device, which had a > version of the database loaded into it? > > Or c) would you write a new app for the device, which made calls > across the web to the existing server side functionality. If you did > this, what technologies would you use for the communication? > > I hope this isn't to vague. I would appreciated any pointers to the > technologies I need to be looking at to achieve this. Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
