Initial Setup | Flangapp AI Docs

Documentation

Login to support

Initial Setup

Start by logging in to your application with the administrator account you created above. On the first login you will see the Initial Setup Wizard. Complete the steps below to finish the initial configuration. You can revisit or change all values later in Dashboard — Settings.

Step 1 — License Activation

Initial Setup Wizard Step 1

You need to activate the license key for correct work of all platform services. Keep in mind that you can only use a license key to activate Flangapp AI on one domain. For each new domain/project you need to buy an additional license.

In some cases you can ask Help Desk to change the original domain. For example, resetting the activation key is possible when you change the test domain to a production domain after the development process.

Step 2 — Builds (updated in 4.6.0)

Choose who builds your users' mobile apps. You can change it later in Settings → Build API.

  • FlangApp builds (recommended) — apps are built on FlangApp's build servers: nothing to sign up for or connect, only the activated license is needed. Every license gets free build minutes (30); after them a minute of build time is paid from your Flangapp AI credits. The minutes left and the price per minute are shown in Settings → Build API, on App download and in the new build dialog.
  • My own Codemagic account — builds run on your Codemagic account (its free plan has 500 build minutes a month) and cost no credits. Needed if you want to build from your own GitHub repository.

With your own Codemagic account, choose where Codemagic gets the apps' source code:

  • Without GitHub (recommended) — Codemagic builds the apps from the public FlangApp template; each app's settings, icons and signing keys stay on your server and are sent to the build when it starts. Nothing to set up on GitHub. FlangApp builds always work this way.
  • My GitHub repository — the apps' source code is kept in a repository in your GitHub account (each app gets its own branch). Choose this if you change the Flutter code of the apps yourself. Installs that built from GitHub before 4.6.0 keep this option.

To connect GitHub you need a GitHub account — create one for free if you don't have it.

  1. Click “Connect GitHub”. The panel shows a code of eight characters.
  2. Click “Open GitHub” (the code is copied), paste the code on github.com and click “Authorize FlangApp”.
  3. Back in the panel, the build repository flangapp_pro is created in your account within a few seconds.

If your account already has a FlangApp repository named flangapp_pro (for example from an earlier install), the panel asks what to do: use it, or create a new one named flangapp_pro_2. Use it if it is left from your previous install; create a new one if another FlangApp install still builds its apps there. A repository with this name that FlangApp did not create is never touched: the panel creates flangapp_pro_2 instead.

Prefer a personal access token? Click “Use a personal access token instead”, open the link to GitHub (it selects the repo and workflow scopes), choose “No expiration”, generate the token and paste it into the panel.

You can connect GitHub later in Settings → Build API.

Step 3 — Connect Codemagic (only with your own Codemagic account)

With FlangApp builds there is nothing to connect: the step only says so. With your own Codemagic account you need the account and its API token; the panel adds the app to Codemagic by itself.

  1. Sign up at codemagic.io.
  2. In Codemagic open Account settings (bottom left) → API token and copy the token.
  3. Paste the token into the panel and click “Connect Codemagic”. Without GitHub, Codemagic gets the public FlangApp template; with your GitHub repository, the panel adds it with a read-only access key. If the app is already in your Codemagic account, it is used.

With your GitHub repository you can also add the app in Codemagic yourself: click “Enter the App ID by hand” and paste the App ID (from the browser address bar of the app's page) and the API token. This step can be skipped and done later in Settings → Build API; until builds are set up, apps can be created and set up, but not built.

Step 4 — OneSignal Integration (optional)

Initial Setup Wizard Step 4

This step is optional: click “Skip” to finish the wizard without it. Apps are then built without push notifications, and you can connect OneSignal later in Settings → OneSignal API. Configure OneSignal to enable push notifications. You'll need your OneSignal User Auth Key and your Organization ID. Firebase Cloud Messaging (FCM) must be enabled in your Firebase project.

Follow the steps below to collect these values, then paste them here.

How to set up OneSignal

  1. You need to register (if not already) accounts on the following sites:
  2. https://onesignal.com/
  3. https://console.firebase.google.com/
  4. After registration go to the Firebase control console and create a new project.
  5. Enable Firebase Cloud Messaging (V1) for your Firebase project. Go to Project settings → Cloud Messaging and ensure it's enabled.
  6. Generate a new private key in Project settings → Service accounts. Keep the JSON key safe and upload it in the wizard.
  7. Create a OneSignal organization at https://dashboard.onesignal.com/organizations/new and note the ID from the browser address bar.
  8. In OneSignal account settings, find “User Auth Key” and copy it.
  9. Paste the Organization ID and User Auth Key into the form.

Step 5 — All Set

Initial Setup Wizard Step 5

Initial setup is complete. You can fine‑tune settings anytime in the Admin panel.

Changing these settings later

Once the wizard is complete, you can revisit any of these values in the Dashboard at any time.

License Details

You can view and change your license anytime in Dashboard — Settings — License Activation.

Build API settings

You can view and change how apps are built anytime in Dashboard — Settings — Build API: switch between FlangApp builds and your own Codemagic account, connect GitHub or another Codemagic account, and see the build minutes left and the price per minute.

OneSignal API Settings

You can view and change your OneSignal configuration in Dashboard — Settings — OneSignal API.

All applications will be created automatically in the OneSignal console as soon as you start building the application. However, OneSignal can not automatically transfer application API keys to create newsletters. You have to enter these values manually for each customer-paid application. If this is required you will see it in the dashboard in the “OneSignal pending apps” section.

When it is possible, you can go to the application settings and enter the integration key:

When you click the external link button a page with a key opens:

Copy the Rest API key and enter it in the “OneSignal REST API key” field.

Until you do this, your client will receive a notification that the mailing service has not yet been activated and it may take some time.

The ability to activate the service appears after the first subscription payment and the creation of the first application build.