. . .

User Interfaces

In contrast to modules that hold backend logic of your app, user interfaces (UIs) contain the frontend code of your app.

You can create your own UIs and share them across your projects. Furthermore UIs may be connected to one or more modules to access your backend data.
ApiOmat Studio Mobile and ApiOmat Studio Web helps you to implement your UI projects. ApiOmat's UI market is the place to orchestrate your UIs.

Relevant Links: Release Notes | UI Market | Modules | ApiOmat Studio Tutorials: UIs for Developer | UIs for Orchestrators

Key Capabilities

Organize frontend projects

Implement your frontend projects and organize them

ApiOmat Studio Integration

Develop your frontend projects with ApiOmat Studio and orchestrate them via UI Market

Module connection

Link one or more modules to your UIs to access your backend data

UI Market

Share UIs across teams via our UI market and configure them to fit your project

How it works

UIs are the components containing frontend code in ApiOmat. The goal is to provide frontends for your modules.
Basically, UIs are ZIP archives which include the frontend project code and some meta data.

In near future, this e.g. enables the possiblity to automatically deploy an UI to a self-hosted website.

Roles and Workflow

In general, you can distinguish between the user interfaces as a template to develop frontends and the backend specific user interface. The idea is that frontend developers can upload such a user interface template with the predefined configuration and everything that is necessary to deploy it. Another person, who just orchestrates the backend application will then add the template to the backend, adjust the UI configuration (which may be, for instance, some color values) and download it to build and/or deploy it then.

To sum up, there are two roles that work together: the UI Developer and the UI Orchestrator. The following table gives an overview of their possible actions and the workflow:



UI Developer

  • 1.) creates UIs

  • 2.) defines the UI template

  • 3.) uploads UIs

  • 4.) shares UIs

UI Orchestrator

  • 5.) attaches UIs to backend applications

  • 6.) configures UIs for backend applications

  • 7.) provide backend specific UIs

More details are available within the sections UIs for Developer and UIs for Orchestrators.