IGEL App Creator Portal
With the IGEL App Creator Portal, you can create apps for IGEL OS 12 by using a recipe and, depending on the case, one or more binaries. The recipe contains the scripts and metadata files necessary to build an app that can be installed and run on the IGEL OS Base System. IGEL, IGEL customers, the IGEL community, or IGEL Technology Partners can provide the recipe.
Legal Note
IGEL is not responsible for, nor does it grant a license to, the applications created via the App Creator Portal.
IT IS YOUR SOLE RESPONSIBILITY TO OBTAIN ALL NECESSARY RIGHTS TO THE COMPONENTS PRIOR TO CREATING AN APPLICATION.
For more information, see our Terms and Conditions:
https://www.igel.com/terms-conditions/
In addition, the App Creator Portal will sign your app and provide the corresponding certificate. When you deploy this certificate to the device, the IGEL OS Base System will allow the app to be installed. Please note there are two types of certificates:
If your company has IGEL Enterprise Edition licenses, you receive a certificate exclusively for your company. With a company certificate, the apps you have created can only be installed on your company’s devices.
If your company has one of the other licenses, you receive a Community certificate. With a Community certificate, your created apps can be installed on any device.

Access to the IGEL App Creator Portal
To log in to the IGEL App Creator Portal, you need an account and have the App Creator role or the Super Admin role assigned. This is done in the IGEL Customer Portal. For details, seeManaging Users and Roles in the IGEL Customer Portal.
Requirements
UMS 12.04 or higher
IGEL OS 12.5 or higher
The recipe for your app
The binary/binaries for your app, if required
Login to the IGEL App Creator Portal
Click Login.

Enter your IGEL credentials.

The landing page of the App Creator Portal is shown.

Every time the page refreshes, all data is cleared and a new isolated session is created in the backend.
Creating the App in the IGEL App Creator Portal
Providing the Recipe
You can provide a recipe by uploading a package file or cloning a Git repository. In the following, we will upload a package file.
Before you upload a package, you may want to check or edit the metadata contained in the following files:
app.json
should contain the correct version and name for your app.igel/thirdparty.json
must contain the names of the binaries used in your app.
You can find a comprehensive description of the metadata at https://github.com/IGEL-Community/IGEL-OS-APP-RECIPES/blob/main/utils/IGEL-SDK-Reference-Manual.pdf- please note this document is primarily aimed at developers who use the IGEL OS App SDK.
Drag & drop your file on the field Upload Package.

The name and size of the file are displayed.

Click Upload.

The recipe is uploaded and processed.

When the recipe has been processed successfully, it is displayed in the right column, and the Create button is active.

For information on cloning a Git repository, see the following links:
Providing the Binary/Binaries
This section is relevant if your app requires one or more binaries. If no binary is needed, continue with Creating the App.
If you upload only a binary, but no recipe, no app will be created.
Put your binary archive / binary archives into a Zip file.
This step is necessary because the App Creator Portal expects a zip file with one or more binary archives inside and performs a corresponding unzipping routine.
Example: To upload the binary archive, e.g.mybinary.tar.gz
ormybinary.deb
, to the App Creator portal, you must first zip it, although it is already an archive file.
The contents of the outer zip file can have the following formats:.tgz
.gz
.zip
.deb
.bz2
Drag & drop your file on the field Upload Package.

Click Upload.

The binary archive is uploaded and processed.

When the binary archive has been processed successfully, it is displayed in the right column.

Building the App
In the right column, click Create.

Review the legal notice in the Notice dialog. If you are sure that all conditions are met, click Acknowledge to proceed.

The build process starts

Once the build process is finished successfully, click Download.

Once downloaded, the uploaded data will be removed after 9 seconds.

Downloading the Certificate
The certificate is required for installing the app on your endpoint devices.
→ Download the certificate from the IGEL App Portal.

You can now deploy the certificate file to your endpoint devices. For instructions on deploying files with the UMS, see Files - Registering Files on the IGEL UMS Server and Transferring Them to Devices (use App signing certificate as the file type). Alternatively, you can deploy the license file locally on the device.
Troubleshooting: Downloading the Log File
→ If something has gone wrong during the build process, download the log file for debugging.

View Your User Details
→ To view your user details, click on the corresponding button.

Your user details are displayed in a dialog window.
