Whitelabel Launch Kit

Overview

Belong delivers a fully branded iOS, Android, and Web experience for eligible organizations: your logo, colors, and domain running on our infrastructure. Payments (Apple Pay, Google Pay, cards, crypto), memberships, events, referrals, and analytics ship out of the box so teams can focus on programs instead of wiring platforms together.

Want the full marketing rundown? Read the public overview at belong.net.

Launch pacing: most orgs go live in under two weeks with standard features; deeper integrations can take longer. The platform fee is waived for qualified organizations (normal payment processing still applies).

Launch Requirements

Prepare the items below before requesting a branded Belong app. Required items unblock build and review; optional items can be added later if they are not ready at launch.

1. App Identity

• Localized app name, with exact spelling for each target language.
• Public domain (https://...) that will host the experience.
• iOS bundleId.
• Android packageName.
• UID slug (2–60 characters).

2. Branding Assets

• App icon (iconOnly, required). SVG is preferred; PNG, WebP, or JPEG can be used when vector artwork is unavailable.
• Icon foreground and background variants (optional).
• Splash screen (required). Layered vector artwork is preferred.
• Splash dark variant (optional).
• Logo (optional, for in-app and marketing surfaces). SVG is preferred for crisp scaling.

3. Experience Settings

• Default theme (auto, dark, or light).
• Onboarding redirect path (must match /activities/... or /hubs/...).
• App switcher disabled? (true / false).

4. Access & Localization

• Desired login providers (facebook, google, apple, phone, siwe, sui) with enable/disable flag per provider.
• Target deployment environment (production or dev).
• Linked App Locale entry (name, description, JSON reference).
• AI chat URL (optional, localized).

5. Store & Support Details

• App Store ID (9–10 digit numeric, optional).
• Support channels with values (telegram, facebook, instagram, x, email, link).

6. Integrations

• Analytics:
  • Meta Pixel ID.
  • Google Analytics ID.
  • Cookie3 Site ID.
  • Plausible enabled? If yes, Plausible API host.
• Google Maps map IDs (iOS / Android / Web).
• SEO metadata (localized): meta title, meta description (50–160 chars), meta image, meta social entries, keywords, robots, structured data, viewport, canonical URL.

Request Flow

1. Gather the launch requirements above.
2. Mark any optional values that should be deferred.
3. Submit the request through the organization request form or Belong support channel.
4. Belong reviews eligibility, confirms blockers, and coordinates the launch timeline.

Localization Bundle

Pull the latest English copy from the JSON bundle below. Share with translators or clone it for additional locales. Keep vector asset preferences in mind when requesting localized splash or icon updates.

How to Request Localization Updates

1. Download the current en.json.
2. Duplicate only the keys you plan to change into a new file (e.g., en.your-whitelabel-name.json). Keep the JSON shape flat: key/value pairs with no extra copy.
3. For each string that needs translation or revision, include:
   • The existing key.
   • The current English value.
   • The requested new value (if already translated) or a comment showing “NEEDS TRANSLATION”.
4. Share that patch file with the Belong team. Belong will merge approved updates and regenerate downstream locale bundles.

Example patch (en.mission-hills.json):

{
  "alert-google-contacts": "Enable Google Contacts to find friends to follow on Mission Hills",
}

Reference Materials

• Canonical marketing copy: Whitelabel App