How to Build Your Whitelabelled Mobile App in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Self-Service Whitelabelled Mobile App Customizer lets agencies brand, build, and publish their own iOS and Android apps directly inside Sparkforge — no engineers and no support tickets.

The Self-Service Whitelabelled Mobile App Customizer lets agencies build, brand, and publish their own iOS and Android apps from inside Sparkforge. No engineers, no support tickets, and live build tracking from start to release.

What the customizer does

It is a guided workspace that handles branding, module selection, store listing prep, App Store Connect / Google Play connections, and one-click build/release controls.

High-level capabilities:

  • End-to-end flow from branding to live publishing
  • Wizards for Apple and Google connections
  • Automatic package and bundle identifier generation
  • Module toggles and navigation layout control
  • Live build status with Internal and Production release tracks
  • Priority access to new app versions

What you get

  • Speed to market — guided steps and pre-checks shorten the path to submission.
  • No dev dependency — release without engineers or tickets.
  • On-brand experience — icons, logos, colors, fonts, modules, and navigation are all yours.
  • Priority updates — get new versions ahead of free apps and choose when to ship.
  • Flexible releases — Internal for testing, Production when you are ready.
  • Operational control — trigger builds, track status, manage changelogs.

Prerequisites

  • Valid D-U-N-S number (Apple requirement)
  • Apple Developer Program Organization account with App Store Connect access
  • Google Play Console Organization account
  • Sparkforge subscription for Custom Agency App (Monthly or Quarterly)
  • Publicly hosted Privacy Policy and Terms & Conditions URLs
  • Apple: Admin or App Manager rights in App Store Connect
  • Google: Admin or Release Manager rights in Play Console

Branding

Configure how the app looks across splash, login, and icons in light and dark modes:

  • App icon at platform-appropriate sizes
  • Splash and login logos (light and dark variants)
  • Primary HEX colors and brand fonts

Use high-resolution square source artwork. Provide both light and dark logo variants. Aim for WCAG-friendly contrast over backgrounds.

Package and bundle identifiers

The customizer auto-generates identifiers using the pattern com.domain.appname_uniqueString when you provide App Name and Domain Name. Do not change identifiers after your first production release — that breaks update continuity for existing users.

Store listing prep

  • App title, short and long descriptions
  • Support email
  • Privacy Policy URL and Terms & Conditions URL
  • Category and keywords (platform-specific)

Migrating from an existing whitelabel app

Keep your existing bundle and application identifiers unchanged to preserve update paths. Sync store listing content into the customizer, and start with Internal builds to validate upgrade behavior before Production.

How to set up the customizer

  1. Open the customizer from Agency view → Mobile App.
  2. Select your app, enter App Name and Domain Name. The system auto-generates a package/bundle identifier.
  3. Open Customisation → Branding and upload icon, login, and splash logos in light and dark variants.
  4. Configure the Login Screen (logo, colors, optional tagline).
  5. Configure Core Navigation. Choose Bottom Nav (4-5 items) or Left Drawer (more items). Add and reorder modules such as Notifications, Conversations, POS, Calendar, Apps. Move overflow into the App Drawer.
  6. Organize App Drawer modules into categories. Add POS (and optionally Invoices/Estimates) to enable Tap to Pay.
  7. Open Distribution → Profile and complete the store listing fields with policy URLs.
  8. Open Distribution → Channels and connect App Store Connect and Play Console via the wizards. Confirm both show Connected.
  9. Choose a Monthly or Quarterly subscription to enable build and publish.
  10. Create the app (first time only), generate a build (Internal or Production), add changelog, and start the build.
  11. Submit in App Store Connect or Play Console. Track status in Live Build Status. If a build fails, click View Progress to diagnose and retry.

Frequently Asked Questions

Do I need an Apple Developer Organization account?
Yes. Apple Individual accounts are not supported for whitelabel publishing.
Can I change the package or bundle identifier later?
Avoid changing it after your first production release. Doing so creates a new app and breaks update continuity for existing users.
What is the difference between Internal and Production?
Internal builds are for testing with your team. Production is the public release in the App Store and Play Store.
My build failed — what should I check first?
Open Live Build Status, confirm both store connections show Connected, validate asset sizes, then re-trigger the build.
How long does store review take?
Timelines vary by Apple and Google. Submitting complete metadata and compliant assets typically speeds approval.

Was this article helpful?