On Thu, Dec 29, 2011 at 2:53 PM, John Goche <[email protected]>wrote:
> The other thing I was wondering was, if I write an android application to > use > appengine and my phone has a web browser, what would make me want to > deploy the service as a data connection to my android application when I > could > just deploy a web service that does the same thing? The only difference I > see > is that the web has a set of UI widgets, and android UI has another but > very > similar API, but allowing access from a web browser seems more flexible > because it means PCs can access it as well. > If you're asking why make a native Android app versus a web app, the answer is access to the Android SDK and device features, like location, sensor, camera, etc, that you can't access from a web app. (I might be wrong about some of those ...) Plus with a native app you don't absolutely need an internet connection to just run. > Also, people who use the application I am planning to design will want to > associate themselves into groups with each group of people having their > own private data space on the web server. How do I cater to the creation > of such groups? Do I get them to register a name on my servlet and > configure a password for them to share? What strategy should I use? > This is a web-site configuration and administration question. If you're going to use AppEngine, they have their own group where you can ask about how to do this specifically on that platform. ------------------------------------------------------------------------------------------------- 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
