I want to deliver an application via a web browser. Perhaps I've developed an application for a small group of folks. I want get the initial application out the door as quickly as possible. A web application (App) that runs within a web browser spares me the overhead of vendor specific devices, operating systems and stores.
HTML5 provides database to persist data across sessions (I.E. offline) in the client.
Offline Processing. In addition to embedded databases, the HTML5 "Application Cache" functions as an install kit for you web application's artifacts. In other words, once installed, you can run a stand alone application.
Our example application will reproduce functions typically performed by the server. For example, we'll produce a new html document, and a "download link" all within the web browser.
File Access. Our project will demonstrate how we can read from and write to the client file system, just like a traditional desktop application.
CSS3 and HTML5 together deliver a rich user interface, cross-platform and light weight. We leverage the web browser to deliver the functionality.
What about a hybrid application, like phone gap/cordova?
To summarize, web technology is more prone to public standards (versus private proprietary application programming interfaces (API)). So, the hybrid strategy has a lot of appeal.
We will go there, but not right away.
Are we going to use libraries?
Later, when we use those great libraries and frameworks, we'll have a good knowledge base to start from.
Note! this is introduction to a series located here.