Native Object API applications are customized, full-featured mobile applications that use mobile business objects (MBOs) to facilitate connection with a variety of enterprise systems and leverage synchronization to support offline capabilities.
The native Object API application model enables the developer to write custom code — C#, Java, or Objective-C, depending on the target device platform — to create a device application.
Development of this type of application provides the most flexibility in terms of leveraging the common application services, but each application must be provisioned individually after being compiled, even for minor changes or updates.
Development involves both server-side—MBO development—and client-side—native application—components. Unwired Server brokers data synchronization and transaction processing between the server and the client components.
- Server-side components address the interaction
between the enterprise information system (EIS) data source and the data cache. EIS data subsets and business logic are encapsulated in artifacts, called mobile business objects, that are packaged and deployed to Unwired Server.
- Client-side components are built into the mobile application and address the interaction between the data cache and the mobile device data store. This can include synchronization frequency, data change notifications, and storage of transactions created offline.
These applications:
- Allow users to connect to data from a variety of EIS systems, including SAP systems.
- Build in more complex data handling and logic.
- Leverage data synchronization to optimize and balance device response time and need for real-time data.
- Ensure secure and reliable transport of data.