Abstract: Techniques are described for receiving a feature request for an application feature of a mobile application. An annotated model class may be determined that corresponds to the feature request and includes class annotations characterizing a server response object stored using an application server and including application data associated with the application feature. An annotated data contract may be determined that includes contract annotations mapping the annotated model class to the server response object and defining a persistence strategy for storing and accessing the application data at an application server and at one or more local caches of a mobile device. A request object may be used to fetch the server response object from the application server. Then, from the fetched server response object and using the class annotations of the annotated model class, a runtime application data model may be generated that is executable by the mobile application platform.

Abstract: Techniques are described for receiving a feature request for an application feature of a mobile application. An annotated model class may be determined that corresponds to the feature request and includes class annotations characterizing a server response object stored using an application server and including application data associated with the application feature. An annotated data contract may be determined that includes contract annotations mapping the annotated model class to the server response object and defining a persistence strategy for storing and accessing the application data at an application server and at one or more local caches of a mobile device. A request object may be used to fetch the server response object from the application server. Then, from the fetched server response object and using the class annotations of the annotated model class, a runtime application data model may be generated that is executable by the mobile application platform.