The mobile app: white label or Beedeez Training

Prerequisite: white label is an account option, enabled on Beedeez’s side, with a contractual implication. See Why can’t I see this feature? Using Beedeez Training requires no option.

On smartphone, your learners install one of two apps: your own, published as a white label on the App Store and Google Play, or Beedeez Training, the Beedeez app already published on both stores. The choice is made at account level and is not permanent: an account launched on Beedeez Training can move to white label later.

The two apps

	White label	Beedeez Training
The app in the store	Yours: your name, your icon	Beedeez Training, shared
Publishing and updates	By Beedeez, on your developer accounts	Already live
Lead time	Formalities, then a store review whose duration is not guaranteed	None
What you gather	Developer accounts, DUNS number, store listing	Nothing
Account option	Yes, enabled on Beedeez’s side	No

What white label does not change

• The inside of the app. Logo, colours and content are set from the back office in both cases. See Customising the learner platform.
• Learner progress. It is tied to the account, not to the app.
• Web access. It stays available whichever app you choose; for populations without a work smartphone, it is sometimes the main route. See Technical requirements.
• Features. Both apps give access to the same features, with the same minimum-version rules.

Moving a live account to white label

This is the most common case, and the one that needs the most preparation: the switch is not transparent for your learners.

• The option is enabled on Beedeez’s side: it is the first request to make to your Beedeez contact.
• The publishing formalities are the same as on day one; see the next section. The account stays usable on Beedeez Training for their whole duration.
• Your learners must install the new app: the old one does not switch over by itself.
• Their progress is preserved, since it is tied to the account.
• Plan the communication. Without a relayed instruction, part of your fleet stays on the old app for months.

⚠️ Treat this switch as a mini-launch, not a setting: it is the path that costs the most in support.

Publishing the white-label app

The formalities with Apple and Google do not depend on Beedeez: start them early, they are the longest lead time of the deployment.

What to gather

• An Apple Developer account of the organisation type, not individual, and a Google Play Console account. Both are paid and created in your company’s name.
• A DUNS number for Apple, if your company does not already have one. Apple requires it to verify your legal entity, and asks for the entity’s own number: trade names and branches are not accepted. Dun & Bradstreet issue it within five business days, then Apple receives it within two more. Start it first: it is the step you control the least.
• The store listing: the images, and the texts described below. The image formats are listed in Visual identity.

Filling in the store listing

You write the store texts yourself, in the back office: Configuration → Customization → White Brand App, in the Textual informations block. The page only appears once the white-label option is active.

• Application name: the name published on the stores, and the one shown under the app icon on the phone. Staying under 18 characters keeps it from being cut off, particularly on iPhone. Check the stores before deciding: a name already taken creates confusion.
• Short description, 80 characters at most, and Long description, 4,000 at most. Both appear in the store search results and on the app’s own page.
• Keywords, separated by commas: they are what makes the app findable in the stores.
• Support email: visible in the stores and in the app, on the sign-in page and behind the help button. This is the address your learners write to, so route it to a mailbox someone reads.
• Assistance url: Apple requires a support page carrying a form, your site’s contact page for instance.
• Marketing url: Apple requires a marketing page, your site’s home page for instance.

Click Save all once the block is complete.

⚠️ Neither description may name your company or present the app as reserved for its employees. A listing judged not accessible to everyone can be refused at review, and the refusal arrives after the wait, not before it.

The access to give Beedeez

Beedeez publishes and updates the app on your behalf; for that, you give Beedeez the necessary access on your publishing accounts. Plan that conversation with your Beedeez contact before starting the formalities with Apple and Google: the order of operations depends on it, and without that access every update becomes a manual operation on your side.

Review by Apple and Google

Once submitted, the app goes through review at Apple and at Google. Review times vary and are not guaranteed.

⚠️ Never set a launch date against a submission date: keep slack, and plan a first wave on web access if the deadline is firm.

Updates on the learner’s side

The app updates from the stores, like any other. A learner who does not update stays on an old version, which blocks features gated on a minimum version. See Technical requirements.

You can change the listing texts and images later. They reach the stores at the next submission, which is heavier than a plain version update and can take longer to clear review.

Using Beedeez Training

Your learners install Beedeez Training from the App Store or Google Play and sign in to your environment. Nothing to publish, nothing to gather: no developer account, no DUNS number, no review. The account can be opened to learners the same day.

The app does not carry your name: in the store, your learners search for “Beedeez Training”, not your company name.

⚠️ Plan an explicit install instruction: exact app name, publisher, screenshot of the icon. Without it, part of your learners install something else or give up. See Pilot and launch.

Going further

• Technical requirements: the minimum iOS and Android versions, and checking the device fleet before opening.
• Visual identity: logo, colours and typography: the formats of the app and store images.
• General options: the behaviour of shared devices and the offline cache size.
• Pilot and launch: the install instruction to give your learners.