Branded UI Builder — bRRAIn Docs

Generate customer-branded mobile, desktop, and browser binaries that wrap your bRRAIn.

Branded UI Builder

Generate fully-branded application binaries — iOS, Android, macOS, Windows, Linux, browser extension — that wrap a customer-specific bRRAIn behind your customer's logo and palette.

Who it's for

  • OEM partners distributing bRRAIn under their own brand.
  • Resellers delivering bRRAIn to many end customers.
  • Enterprise IT issuing an internally-branded bRRAIn app to employees.

What it does

You provide:

  • A logo (SVG and PNG sizes).
  • A palette (primary, secondary, accent).
  • A bundle ID and app name per platform.
  • A signing identity per platform.

The Builder produces signed binaries for each platform you opt into:

  • iOS .ipa ready for App Store submission or enterprise distribution.
  • Android .apk and .aab ready for Play Store or sideload.
  • macOS .app, notarized .dmg.
  • Windows .exe and signed .msi.
  • Linux .AppImage, .deb, .rpm.
  • Chrome extension .crx ready for the Web Store.
  • Firefox add-on .xpi ready for AMO.

Every binary points at the same backend — your customer's bRRAIn — and inherits your customer's identity providers, branding, and policy.

Installing

Per-organization subscription. The Builder runs as an extension inside your Console. Building binaries is metered (per-build, per-platform).

After install, you'll be guided through:

  1. Provisioning a signing keystore (Apple developer cert, Android keystore, Authenticode cert, etc.). For most flows you upload existing certs; for some platforms we can broker fresh ones.
  2. Setting your default brand profile.
  3. Building your first binary set.

Brand profiles

A brand profile is a saved bundle of:

  • Logo, icon, splash screen.
  • Color palette.
  • Typography.
  • Bundle ID and app name.
  • Distribution channel metadata (App Store description, Play Store keywords, etc.).

You can have many brand profiles — typically one per customer — and switch between them when triggering a build.

Builds

Trigger a build from the Builder UI or via API:

  1. Pick a brand profile.
  2. Pick the target platforms.
  3. Pick the bRRAIn backend the binary should connect to (typically your customer's organization).
  4. Optionally pick a feature-flag set (e.g., enable specific marketplace extensions in the wrapper).
  5. Submit.

Builds run on dedicated build agents. Typical times:

  • Browser extensions: 1–2 minutes.
  • Android: 3–5 minutes.
  • iOS: 5–10 minutes (signing + notarization).
  • macOS: 5–10 minutes (notarization).
  • Windows: 3–5 minutes (signing).
  • Linux: 2–3 minutes.

The output appears in the build artefacts panel as downloadable signed binaries with checksums.

Submission helpers

For App Store and Play Store, the Builder includes submission helpers:

  • Auto-populates store metadata from the brand profile.
  • Generates store screenshots from a template.
  • Wraps the upload to App Store Connect / Play Console.
  • Tracks review status and surfaces rejections.

Distribution

For non-store distribution:

  • We can host signed binaries on customer-specific URLs at your-customer.brrain.io/install.
  • For enterprise iOS distribution, we can issue MDM-compatible profiles.
  • For Windows, we can wrap into MSI for SCCM / Intune deployment.

Update channels

Each binary is wired to phone home for updates:

  • Stable channel (default).
  • Beta channel (opt-in).
  • Pinned to a specific version.

Updates are delta-encoded where possible to minimize download sizes.

Scopes required

  • Read and write in the extensions/branded-ui-builder zone.
  • Access to the customer organization's branding settings (read-only).
  • Build agent compute provisioning rights.

Where to next