Sybase Mobile SDK

Sybase Mobile SDK provides development support for Native Object API Applications, HTML5/JS Hybrid Applications, and OData SDK Applications.

The end result of the development process is a packaged mobile application ready for provisioning to devices. The following diagram shows the device application structure and services provided for each of the development approaches with Sybase Mobile SDK.

Dashed outlines in the diagram represent the services provided by Sybase Mobile SDK for each application type. Native code development outside of the Mobile SDK uses APIs that support core services and application specialization, in addition to leveraging in-house device platform development expertise.

Core Application Services – The set of common services provides a consistent foundation upon which mobile apps are developed. These common device services make development easier and more secure.
Security features are embedded into the SDK to support secure storage of certificates, use of the artifacts in authentication, single sign-on, and other features related encryption of the database. APIs are supplied to support certificate store, logon certificate, and the data vault. Each application type makes use of the same set of security features.

Application Specialization – Application specialization is the differentiator between development approaches. Based on these distinct application services and your business needs, develop one or more application types.

Develop Apps with	When your business needs
Native Object API SDK	Offline applications: Mission-critical and more complex. Users work on data offline and synchronize updates to the server when connected.
HTML5/JS Hybrid App SDK	Online applications with Push: Simple queries and workflows that follow a request-reply or lookup pattern.
OData SDK	Online applications with Push that use OData protocol: Data, modeled in SAP Gateway, is accessed in a request-reply or lookup pattern.

Synchronization implies an intermediary store of cached data and the process by which data changes are propagated between the server, the cache, and the device storage with the goal of ensuring that the data is replicated in each location.

Push leverages a proprietary message transport to move data between device and server. The data change is initiated, or pushed, from where ever the data change takes place: from the device if the change takes place there, or from the server if the change takes place there.

Business Logic and Device User Interface – The user interface is developed:
- Using the developer IDE of choice for the target device platform and either the Native Object APIs or the OData SDK APIs.
- Using the Mobile Workflow Forms Editor to design HTML5/JS.

Native Object API Applications
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.
HTML5/JS Hybrid Apps
HTML5/JS Hybrid Apps support simple business processes, such as approvals and requests, and also use mobile business objects (MBOs) to facilitate connection with a variety of enterprise systems. With this approach, a container is developed and deployed to a device, then one or more workflows are deployed to the container. This approach supports mobile workflow enablement, which enables mobile device users to operate as workflow participants, allowing the mobile user to start and respond to back-end enterprise requests within a generic framework.
OData SDK Applications
OData SDK Applications are simple, mostly online mobile business applications that leverage standards-based approaches—OData protocol and RESTful Web Services. This approach provides instant quick value applications meant for end user productivity.
Development Life Cycle
The "development life cycle" takes developers through the process of designing, developing, testing, deploying and maintaining mobile business objects, device applications, and workflow packages.