Here is a simple application I built using j Query Mobile and Phone Gap.
Even though the application is simple, it covers some common requirements of mobile applications: database access through JSON services, multi-level master-detail views, parameter passing between views, etc.
An application developer directly uses an API to locate records either by their key or by using an index. An indexed database can be implemented using a persistent B-tree data structure.
This is the W3C Recommendation for the Indexed Database API.
Changes to this specification since the previous publication are summarized and enumerated in this document's Revision History appendix.
This specification's bugs and issues are managed in Bugzilla (new bug, open bugs).
Feature requests for the next version of this specification are kept in the Indexed Database Features document.
This document was published by the Web Applications Working Group as a Recommendation.
If you wish to make comments regarding this document, please send them to [email protected](subscribe, archives). Please see the Working Group's implementation report.
This version of the application doesn’t use any of the Phone Gap native APIs (GPS, camera, accelerometer, notification, etc).
In my next blog post, I’ll show the same application getting the data from a local database (using the Phone Gap database API) as opposed to PHP services.
Please check the errata for any errors or issues reported since publication.
The English version of this specification is the only normative version. Copyright © 2015 This document defines APIs for a database of records holding simple values and hierarchical objects. Moreover, the database maintains indexes over records it stores.