Outside of arcade games or building yet another app, and the like... Where solid research is needed and missing (to my knowledge) is how web apps using the newest vehicles (HTML5, Gears, Ajax) compare against native apps with regards to usability, demands on carrier capacity and so forth. Being able to get an app up and running as a web app has obvious advantages, and has been pitched as the new way of implementing mobile apps at Google I/O this year. The given constraints can be quite serious though. Carrier network capacity is one, as the hoopla around an upcoming commodity upgrade of AT&T's network here in the US illustrates. You could write a few prototype apps for a few use cases such as shopping, gaming, visualization, LBS using Google Maps API Android native vs. web etc. Find out how they perform against each other under a variety of conditions (3G, 2G, strained networks) and how the underlying technologies allow designs that can meet user expectations.
On Sep 5, 5:03 am, fukazzz <[email protected]> wrote: Actually, I am quite free in my choices as I said before. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
