Developing iOS, Android, and Windows Offline OData Applications

Understand how to develop a native iOS, Android, or Windows application that uses an offline OData store.

The basic flow of developing a native application that consumes online OData versus offline OData is the same: registering devices and connecting users, performing create, update, delete operations on the entity uses the same APIs. The main differences involve:
  • Initial database creation A database is created and populated during initialization that stores a subset of the OData endpoint data, based on your defining requests.
  • Flush Updates from the back end. Includes support for conflict and error detection and resolution.
  • Refresh Updates from the client.
See Native OData Offline Task Flow for details.