The development of a Mini App is similar to the development of any native application with GeneXus, with the following characteristics:
- A Mini App is an application that will be executed within the Super App domain.
- It is composed of “metadata” (a .gxsd file that will be rendered as a native app) and backend services.
A Mini App makes sense in the context of a Super App. Therefore, the first step for you to take is to register as a developer of a certain Super App (especially if you’re developing a Mini App for a Super App external to your organization). In this way, you’ll get all the necessary resources to carry out the integration, that is, the Super App API and the eventual design and interaction resources that it provides.
During the development stage, you will have to import the API of the Super App, in order to program the invocations to the services that it exposes.
Besides, it’s necessary for you to install the GeneXusMiniApps Module. It provides additional resources to interact with the Super App (for example, the Exit method to return to the Super App).
The Mini App is loaded dynamically from the Super App, so certain restrictions apply with respect to any other GeneXus app:
- It has to be an online app.
- The use of User Controls and Extensions will be limited to those declared in the Super App.
Finally, to be able to test your Mini App integrated to the services of the Super App, you should have a sandbox version of the Super App.
Once you have completed the development and testing of the Mini App, the next step is to submit it for review.
This requires you to deploy the Mini App backend services in your production environment and catalog the Mini App metadata for review through the Mini App Center.
You can see the details in Mini Apps articles.