. . .


Develop Apps faster than ever with ApiOmat SDKs. Each project's SDKs are individually generated for each of your projects, so you can quickly build apps for any device – using native, cross-platform or web development.

Generate SDKs that are unique to your app and immediately start building the UI and frontend logic. ApiOmat SDKs are source code that any developer can work with. The SDKs include mobile and web app services, but also include all the data models in the frontend programming language. Developers no longer have to consume APIs, and they can start developing apps with the programming language they know best.

Tutorials: Android | iOS | Swift | C# | JavaScript | Xamarin | Java | TypeScript

<div class="videoBox">
<iframe width="560" height="315" src="https://www.youtube.com/embed/BRnnML8kVNs?rel=0" frameborder="0" allowfullscreen></iframe>

Key Capabilities

Frontend Flexibility

SDKs for iOS, Android, PHP, Java, JavaScript, C#, ...

Individualized SDKs

ApiOmat generates SDKs based on your app’s backend and not only generic services.

Frontend Data Models

ApiOmat SDKs include all the classes from your app’s backend and support offline handling, caching, querying and error handling.

Source Code

ApiOmat SDKs are source code and automatically documented. JSON conversions and connection handling is also done transparently.

How it works

When downloading SDKs, all meta-information from the app backend like used modules, classes, and relations are taken into account and source code for the selected programming language is generated instantly. This enables the developer to work with the very same data models designed in Dashboard or in the attached modules, eliminating risks of data transformation and making changes of the data modeling very insusceptible to errors.

Not only the source code for the data models is included in the SDKs but many other static features: First of all, the complete handling of network access is included and made transparent for the developer. Error handling, POSTing, GETting, etc, all is available through save() and load() calls on the data model. Furthermore, caching is implemented using the modified-since header and etags to limit unnecessary traffic.

To enable working apps without network access, offline handling features are implemented in the SDKs, which makes working with the data models possible when being offline and starting a synchronization of the data with the server when gaining online access.