This blog is also a great example : technically, it’s an app, and yet, it’s made of static HTML files, hosted on Github as well. I think these 2 examples can give us a “hint” on what Web apps will look like in a not so distant future :
- A bunch of static HTTP files with CSS, served by clusters
- Some AJAX to send and receive data from one (or more) application servers, through APIS (JSON, or XML)
The great thing about that is that web services (and developers) can focus on a single “job”, while designers, UX engineers can ‘pick’ up whatever tool they want to integrate into an app and make it richer.
With this approach, you can really decouple more and more the data and the processing from the views. The APIs can very well be consumed by a webservice, but also by, say, an iPhone App, an Adobe Air App, or even external web services and we sites.
This should sound familiar, doesn’t it? It’s very close from the MVC model that we all learnt to create desktop apps.