Phone Borneo

When AJAX was off on it is extended journey from Desktop to Mobile the "Model View Controller (MVC)" legion descended on the desktop net programming planet. MVC has been hidden in anything from ASP.NET, to PHP, to Ruby On Rails. The dirty tiny secret of MVC style programming is that it confuses the conventional "3 Tier Programming" model. The presentation layer (User Interface) and application logic gets all gummed together considering that the UI gets driven straight by processing that occurs exclusively on the web server. On the desktop, MVC isn't fatal due to the fact desktop computer systems are typically connected with rapid broadband pipes all the time. On mobile, having said that, native apps have exposed the soft beneath belly of that paradigm - who desires to wait for a round-trip to the server each and every time the user does one thing on their phone?

We need to all take a moment to appear at mobile net internet sites and consider what life would be like if they all felt a tiny bit significantly more like native iPhone apps. Why must mobile net websites impose a worse knowledge exactly where users wait even though pages constantly reload. How can we make the experience really feel "a great deal more native"? Properly, that's what AJAX is all about. How can we get there? As Agent Oso says "Three specific actions - that is all you have to have" (extra credit for recognizing the reference):

Step 1: Implement UI in JavaScript and HTML5

3D transforms, spinners, multi-touch, swiping, and all kinds of excellent UI effects are exposed in the WebKit based browsers including iOS, Android, Symbian, WebOS, and Blackberry 6.

Step 2: Use PHP, ASP.NET, and so on. only to expose data transfer net solutions

Don't use PHP or other server side technologies to layout the client-side UI. Server-side technologies are very best for getting a conduit to data. Use them to format data in XML or JSON for consumption on the client-side of your web applicaiton.

Step three: Assume "offline"

Style you app as if it will need to be useful even when your user is on a plane with no internet connection. HTML5 and appMobi expose extensive caching mechanisms. Every little thing from pictures to information can be cached on the device. Just about every image and just about every piece of data that has to go over the network is a separate request to a server - it makes factors unbearably slow quite often. Cover the offline case first and the on the net case becomes very easy. It also will comply with that your users will have improved experiences with your brand regardless of their network connectivity.

In software, as in fashion, if you wait lengthy sufficient items come back in vogue. Now, we welcome back AJAX from its travels and we boldly predict it really is future dominance. On the desktop net, AJAX was caught in the cross-fire amongst browser incompatibility and muddy waters of Flash, Java, and desktop apps written in C++ or.Net. On mobile intelligent phones, the globe is fundamentally unique - with WebKit and HTML5 browser compatibility on mobile is in particular beneficial. In a framework like appMobi exactly where a broad range of native functionality is exposed via JavaScript - the need for complicated languages like C++ and Objective C is eliminated for all but the most obscure functionality. In oversimplified on mobile, AJAX finally has an chance to reside up to it is hype. It will aid "open web" technologies supersede Flash and, in doing so, make the "native app" vs. "mobile web web site" argument moot.