Branding & config

A white-label app is configured to look and feel like your product — logo, colours, landing content, and the in-app tour. This configuration is managed with AURA: you supply the brand inputs below, and AURA builds and publishes the branded app from them.

What you supply

App identity & behaviour (captured in your brand configuration):

• Brand name, bundle/application ID, and your AURA clientId.
• Support contacts — support email and contact number.
• Country/calling code defaults and (optionally) a default language.
• Product type — personal-safety or fixed-location — which shapes the panic journey the app presents.
• Subscription options — which payment routes the app offers (hosted gateway, your own third-party gateway, and/or access codes).
• Feature choices agreed during onboarding, such as medical-information fields, coverage display, language switching, and whether customers can deactivate their own subscriptions in-app.

Theme & content:

• Colour palette (panic button, backgrounds, header, menu) and typography choices.
• Logos, app icons, splash screens, and any additional onboarding/tour screens.
• Terms & conditions document, and landing/tour copy.

Store & services credentials (see Apple Developer Account and Google Play Account):

• Apple App Store Connect access for your account, and an Android signing keystore + Play Console access (a Huawei AppGallery account can also be supported).
• Firebase apps for your bundle IDs (push notifications and dynamic links are configured against them).

How it reaches the app

AURA bakes your brand configuration into the app build and also serves branded content (landing and tour screens) to the app at runtime through white-label config endpoints.