> ## Documentation Index
> Fetch the complete documentation index at: https://internal.softcrum.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ADR-020 — Mobile White-Label Strategy (Expo + React Native)

> Apple guideline 4.3 and white-label policy push per-tenant binaries to the CLIENT's own developer account; per-tenant build pipelines are operationally expensive.

Status: Proposed · Refs: DEC-F2, DEC-F3, Q-28/Q-29

## Context

Apple guideline 4.3 and white-label policy push per-tenant binaries to the CLIENT's own developer account; per-tenant build pipelines are operationally expensive.

## Decision

First: ONE multi-tenant member app ("powered by Softcrum") with runtime theming (tenant discovery via deeplink/code/email), architected for extension — tenant config (theme, bundle metadata, entitlement flags) lives OUTSIDE code from day 1 as EAS build profiles + remote config, so the premium tier (dedicated binary under the client's Apple/Google account, paid add-on) is a build-pipeline addition, not a rewrite. Middle layer: wallet passes (F2, own small ADR) — **always issued under Softcrum's own accounts**, never the client's: a pass has no store listing, so guideline 4.3 does not apply and the branding travels inside the pass file. A tenant wanting a channel entirely under their own name buys the dedicated binary instead (corrected 2026-08-17, FS-LOY-0014). Push via FCM/APNs; Live Activities (F2) will require Expo dev-client + native module (its own ADR).

## Consequences

* One listing to maintain; premium tier priced to cover its real ops cost. − Single-app tier can't use tenant's own icon/name (explicitly sold as such).