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
- Refresh Updates from the client.
See Native OData Offline Task
Remember When writing an offline app, it always accesses data stored in the
offline store, regardless if the device is connected to the network or not. Do not
attempt to switch between online and offline mode. In other words, an offline app
does not sense that it is connected to the network and switch to “online” mode, or
switch to “offline” mode when disconnected from the network.
Restriction The Offline OData SDK for Windows does not support using client
certificates to perform mutual authentication with the server.