Skip to main content
An App is one mobile or web application connected to the Synheart Platform. Apps live inside a project, and each app is the unit where you configure API keys, attestation, policy, consent profiles, and Syni. This page covers registering an app, the app workspace, downloading credentials, and editing or deleting an app. For first-time onboarding context, see the Developer portal.

​
App identifiers

Each app carries two distinct identifiers; don’t conflate them:
The registration form labels the store identifier field App ID / Package Name, but that value is your bundle_id, not the platform app_id. The platform app_id is generated for you and appears in credential downloads and support references.

​
The apps list

Open Apps from the project sidebar. The page shows all apps linked to this project. Each app appears as a card showing its name, platform badge (OS), and its identifier line. A results line reads {filtered} of {total} apps.
  • Search: match by name, description, or category.
  • Filters: narrow by Category and Operating system chips; Reset filters clears everything.
  • Clicking a card opens that app’s workspace at Sessions.
Card hover actions include Edit app, Purge analytics data, Delete app (owner only), and Remove from project.

​
Register an app

Apps must be created inside a project. From Apps, click Add App to open the Add New App drawer (“Add a new app to this project and start tracking ingestion.”) and complete the form:
Use Auto-fill after entering the OS and package name to pull store metadata (name, icon) automatically.
The optional SDK Configuration block pre-seeds attestation settings: Google Project ID and Allow development builds on Android, or Apple Developer Team ID and Allow development builds on iOS. You can also configure these later in app settings. On success, the platform assigns the app a platform app_id and links it to the project.
During early access, registering new apps may be disabled and replaced with an early-access notice.

​
The app workspace

Opening an app switches the sidebar to App navigation and shows a header card with the app icon, name, the platform app_id (monospace), and the category. A breadcrumb reads Projects / {project} / Apps / {app}. The app landing route redirects to Sessions; there is no separate overview tab.

​
Download app credentials

The workspace header has a Download App Credentials (.json) button. It produces an app-credentials.json file containing the four non-secret identifiers your SDK and tooling need:
This file contains no secrets. To download credentials that include the secret key and signing secret, generate them in the one-time dialog under API keys.

​
App settings

Open App settings from the app sidebar. The page covers app details and SDK attestation; this section documents everything except the attestation block (see App attestation for that).

​
App details

Click Edit to make the App details fields editable, then Save changes:
The package name / bundle ID is set at registration and is not editable on this page. Register a new app if you need a different store identifier. During early access, editing app details may be disabled.

​
Danger zone

After a purge, a confirmation shows approximate row counts removed (HSI, lab metadata, lab sessions). Deleting an app returns you to the project apps list.

​
Remove vs. delete

​
Next

API keys

Generate and scope per-app keys for the SDKs and your backend.

App attestation

Configure Play Integrity (Android) and App Attest (iOS) for the app.

App policy

Set what data the app may collect and where it may be processed.

Connect & view data

Connect a wearable and inspect the session data the app produces.