⚙️ Settings
App name, icon, store identifiers, signing keys and team access.
Settings holds the details about the app itself rather than its contents: what it is called, how it is identified in the app stores, who can open it, and how to delete it.
Six sections. General is open by default.
General
Section titled “General”App name — the name of the app. If it is left blank when the app is created, it is titled “Untitled App”, and Ada can rename it later.
App Icon (1024px × 1024px) — drag an image onto the drop zone or click to choose one. A square PNG at 1024×1024 works best. Once set, the icon is shown in place and hovering offers Change.
iOS Settings
Section titled “iOS Settings”Bundle ID — the app’s unique iOS identifier, in reverse-domain form, for example com.acme.myapp.
App Store Connect
Section titled “App Store Connect”Your iOS app is signed under your Apple account, not Adalo’s. This section holds the API key that makes that possible.
Create the key in App Store Connect under Users and Access → Integrations → App Store Connect API, with the Admin role. Then supply four things:
- Key ID — for example
ZQU8U6M36D - Issuer ID — a long identifier, for example
09e5ed75-66cb-… - Team ID — for example
9VYG78W35D - API Key (.p8) — the key file itself
The .p8 is stored encrypted and never shown again.
After it is saved
Section titled “After it is saved”Once connected, the section shows what is stored: the three identifiers in read-only fields, and the key itself as Stored, encrypted. One Edit button unlocks them.
While editing, the upload row reads Keeping the stored key — choose a file to replace it. Save changes saves, and Cancel discards what you typed and puts back what is stored.
Warning
Apple lets you download a .p8 exactly once. Keep your copy somewhere safe.
You do not need it again to correct a typo — an edit keeps the stored key unless you choose a new file — but you cannot recover it from Adalo, because it is never shown after saving.
Android
Section titled “Android”Bundle ID — the app’s unique Android package name, in reverse-domain form, for example com.yourcompany.app.
Ready to publish
Section titled “Ready to publish”A checklist of what is still missing before the app can go to the stores. It covers naming the app, adding an icon, connecting any integration the app’s code uses, and adding the App Store Connect key.
Each item links to the panel that fixes it, so the list is a route rather than a report.
App Access
Section titled “App Access”Who can open and edit this app.
Team admins can always open it. Everyone else has to be added here, and the list shows current members alongside any pending invites.
Only team admins can add or remove people; for everyone else the section says so rather than showing a control that will not work. If your team list cannot be loaded, the panel says that too — an empty roster and a failed load look identical otherwise.
Danger zone
Section titled “Danger zone”Delete this app removes the app’s code, chat history, versions and preview permanently. It cannot be undone.
You are asked to confirm by typing the app’s name. If the app is still generating and its name is not known yet, you are asked to type DELETE instead.
Danger
Deletion lives in Settings rather than in the chat header on purpose. It is irreversible and does not belong beside the everyday controls.