Obviously there are some applications that can be built easily for a mobile web browser. When starting a new mobile project, I guess it's worth doing some initial analysis to determine if your application stands to benefit from being a web-based app. Many main stream mobile gurus make claims that the future is AJAX on the mobile browser. Not being a guru myself, my opinion probably counts for not. Nevertheless, I don't like JavaScript nor do I care for AJAX (and not really Flash or Silverlight either). I think most mobile browsers leave too much to be desired, to consider building any app. I want to build, for a mobile web browser (iPhone included). Plus, web apps. don't give you freedom they take it away (i.e. no phone interaction because of security sandboxing). I personally hope mobile web apps. never catch on.
I once thought Palm Web Clipping applications would change the game for native apps. I don't think they ever really did. I don't think mobile web as a killer application deployment platform will either. I think this guy is selling snake oil (http:// opengardensblog.futuretext.com/archives/2006/01/mobile_web_20_a.html). The mobile web curmudgeon On Jun 7, 12:01 pm, chaosvoyager <[EMAIL PROTECTED]> wrote: > I know this question is not directly related to Android, applying to > mobile platforms in general, but I wanted an Android developer's > opinion. > > So how important is web browsing on a cellphone? Is it important > enough to be on every phone? If so, then why not extend it to become > the platform itself? > > My reasoning is thus: > > XML APIs and Javascript (AKA Actionscript and ECMAscript) will already > need to be present, and extending Javascript with types, threads, and > APIs to access phone functions/sensors would not be too difficult. > > It is also easier to extend existing web apps with additional features > than writing them over again. For example, Adding GPS to the existing > web based Google maps should take just a few lines of code if the APIs > are done right. > > And JIT compiled Javascript can achieve the same performance numbers > as Java at this point, though any time you reduce the memory footprint > of a VM, you compromise performance. Besides, if you really need the > best performance and deterministic behavior possible, C will still be > there. > > So, what says your gut? --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
