Your productSeveral brands

You are building an app with AI for several clients or brands. MainPath keeps the codebase shared and prepares separate builds, domains and store listings for each variant.

Develop shared features. Keep each brand’s values in its own configuration.

One ideaTwo identities

Studio and Bloom are example brands for the same product. Their features stay shared, while each configuration supplies its own brand properties.

Studio

Example: its own logo, colours and studio.example domain.

Bloom

Example: different branding, bloom.example and a separate store listing.

What you build togetherWhat each brand defines

The shared codebase

  • Develop features and fixes in the same project.
  • The app reads the values of the selected variant.
  • Components not marked as whitelabel can remain shared.

The individual variant

  • Name, logo, colours and other fields in the variant schema.
  • Separate web and backend domains, plus individual app identifiers.
  • A separate build and deployment for each brand.

The app must use the variant fields. MainPath does not create new designs or product features from them on its own.

Each brand in the storeWith its own content

Separate bundle IDs and package names distinguish the apps. Maintain store copy, screenshots and release notes in the project; the pipeline handles the prepared uploads.

  • Store access and signing material need to be configured.
  • Test the build for each brand before submitting it.
  • The store decides whether to approve the submission.
Explore store content

From the base to the next brandOne workflow for your variants

  1. Set up the base

    Create the shared product. Select whitelabel deployment in the project editor’s pro mode.

  2. Define the differences

    Create a schema for names, colours, logos and other brand properties. Connect those fields to the app.

  3. Fill in the variants

    Set values, domains and app identifiers for each brand. Connect the required accounts for store releases.

  4. Test and release

    The pipeline builds each variant separately. Check the results and decide which version to submit for store review.

The next brandOn the same foundation

Start with a shared product and define what needs to differ for each brand. We can help you find the right way to begin.

Questions about whitelabel apps

How do I create a whitelabel project?

Choose whitelabel deployment in the project editor’s pro mode. Then define a variant schema and add the brands with their values. If you are new to MainPath, get familiar with builds and deployment in a regular project first.

Explore whitelabel mode

How does the branding reach the app?

Whitelabel components connect fields such as the logo, colour or app name to your application. The shared codebase reads the values of the current variant. Set up these bindings in the project yourself or with your AI agent.

Can the brands have different features?

The variant schema can include yes/no fields and other settings. Your app needs to implement those differences in code. If the logic and roadmaps diverge substantially, a separate project may be a better fit.

Does every brand have a separate store listing?

Each app variant is submitted with its own identifier. You need the appropriate developer accounts, access and complete store content. MainPath prepares builds and uploads; Apple or Google review the submission and decide whether to approve it.

Do we have to copy the backend for every brand?

No. Components not marked as whitelabel can remain shared. A shared backend can serve several brands. You decide whether your application’s data and services should be shared or separated.

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab