Studio
Example: its own logo, colours and studio.example domain.
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.
Studio and Bloom are example brands for the same product. Their features stay shared, while each configuration supplies its own brand properties.
Example: its own logo, colours and studio.example domain.
Example: different branding, bloom.example and a separate store listing.
The app must use the variant fields. MainPath does not create new designs or product features from them on its own.
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.
Create the shared product. Select whitelabel deployment in the project editor’s pro mode.
Create a schema for names, colours, logos and other brand properties. Connect those fields to the app.
Set values, domains and app identifiers for each brand. Connect the required accounts for store releases.
The pipeline builds each variant separately. Check the results and decide which version to submit for store review.
Start with a shared product and define what needs to differ for each brand. We can help you find the right way to begin.
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.
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.
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.
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.
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.