Set up your white-label mobile app

Use this guide after your organization has agreed the service scope, one-time setup fee, additional recurring service fees, and expected timeline with coapp. A white-label app requires manual setup through the coapp team; it cannot be enabled in the coapp web app.

Complete the steps in order where possible. Account verification, internal approvals, and store review can affect the publication date. If your service is already confirmed and contacts are assigned, start with step 3 for Apple and Google account setup, then continue with app records and access in steps 4 and 5.

coapp configures the app and handles technical builds, submission, and technical updates. Your organization supplies brand assets, store screenshots, descriptions, keywords, and community-specific information, approves the prepared app and store presentation, and retains responsibility for its publisher accounts and legal information. Reuse existing accounts, community settings, and suitable legal pages rather than creating them again for the app.

1. Confirm the service with coapp

Contact sales@coapp.io or use the customer-support chat in the coapp web app. Confirm:

• which community the app will open;
• the included service and expected timeline;
• the one-time setup fee and additional recurring service fees; and
• how your team will exchange assets, credentials, approvals, and status updates with coapp.

Apple and Google account or store fees are separate and remain your organization's responsibility.

2. Assign responsible contacts

Tell coapp who is responsible for each part of the project. One person may cover several roles, but every decision needs a named owner.

• Project contact: coordinates deliverables and day-to-day questions.
• Store account owner: completes verification, agreements, payments, and access changes.
• Brand approver: approves the app name, icon, splash screen, colors, screenshots, and store presentation.
• Legal or privacy contact: approves policy URLs, data-use answers, age rating, and distribution information.
• Release approver: gives final approval for submission and publication.
• Operations contact: owns member support, moderation, and privacy requests after publication.

3. Create or verify your organization store accounts

Your organization must own the store accounts and remain the legal publisher shown in the stores.

These store accounts are separate from your coapp subscription and members' Community Accounts. An Apple Account or Google Account is the login; the developer account is the publishing membership you set up with that login. App Store Connect and Google Play Console are the portals where you manage your app's store entry and releases.

Use the desktop web portals for the steps below. Control names refer to their English interfaces; names may differ if you use another interface language.

3.1. Prepare your organization's information

Gather the following before starting either enrollment:

What to prepare	What you need it for
Registered legal name and address	Use the same organization details in registration documents, Dun & Bradstreet records, and store forms. Your community or brand name may differ from the legal name.
D-U-N-S number	A nine-digit business identifier from Dun & Bradstreet, used to verify the legal entity. Check for an existing number before requesting another.
Public organization website	Use a working website that identifies your organization, with access to the person who manages the domain and website.
Work email and reachable phone	Keep access to verification emails, text messages, and calls throughout setup.
Authorized representative	Choose someone who can accept agreements for your organization and remain responsible for the account. Apple requires the legal age of majority; Google requires an account owner aged at least 18.
Organization documents and photo ID	Keep registration documents and the representative's valid government-issued ID available for verification requests. Upload these directly to the store's verification process.
Payment method	Arrange approval to pay the separate Apple and Google developer fees.

Start with the Apple D-U-N-S lookup and request guidance. If your legal entity already has a number, use that entity's number for both stores. Check the registered name, address, and legal status before continuing. A D-U-N-S number is different from a tax number or company registration number.

Requesting a number through the standard enrollment route is free. Plan ahead: Google's guidance says obtaining one can take up to 30 days; Apple also needs time to receive new or corrected records from Dun & Bradstreet. Government organizations have exceptions; Google's guidance also covers unsupported regions. Follow the relevant Google organization-account requirements rather than entering a substitute number.

Already have store accounts? Ask your organization’s account owner to sign in and confirm the legal entity, account type, active Apple membership, completed Google verification, and outstanding agreements. Reuse the correct accounts. If the account belongs to a person, another legal entity, or an agency, resolve ownership with coapp and the store before continuing.

3.2. Enroll in the Apple Developer Program

For an organization-owned App Store app, use the Apple Developer Program. Apple's Enterprise program serves a different distribution purpose.

1. The designated account owner opens Apple Account and signs in or creates their own account. Enter that person's real first and last name. Keep the login and recovery options under that person's control within your organization.
2. Enable two-factor authentication for the Apple Account and confirm that the owner can receive verification codes. See Apple's two-factor authentication instructions.
3. Open Apple Developer Program enrollment and select Start your enrollment. Sign in with that Apple Account and complete the requested personal information.
4. Choose the organization entity type that matches your registered legal entity. Enter its legal name, D-U-N-S number, address, website, and work contact details. Use an email address on your organization's domain.
5. Confirm that you have authority to enter into agreements for the organization. If you are not the owner or founder, provide the reference Apple requests to confirm your authority.
6. Submit the enrollment and monitor Apple's emails and calls. Provide additional evidence if requested; Apple may ask for certified organization documents. The enrollment is still pending at this point.
7. After Apple verifies the organization, follow its email instructions to accept the program agreement and purchase the membership. The standard fee is US$99 per year, with regional pricing shown during enrollment. Eligible organizations can check Apple's fee-waiver option before paying.
8. Wait for membership confirmation, then sign in to Apple Developer and App Store Connect. Confirm that the correct organization is selected and the membership is active. In the developer account, open Membership details and record the Team ID for the handover to coapp.

The enrolling person becomes the Account Holder. Keep that role in your organization. Apple's seller name is the legal entity's name, even when the app uses your community's brand name. Sole proprietors and single-person businesses enroll as individuals with Apple; discuss that case with coapp before proceeding because the personal legal name appears as the seller. See Apple's enrollment requirements.

In App Store Connect, open Business → Agreements and review outstanding agreements. The Account Holder accepts the required agreements. For the trader declaration, go to the Compliance section on that tab and select Complete Compliance Requirements beside Digital Services Act when shown. Have your legal contact confirm the correct status, then complete the requested contact verification and evidence. Trader contact details are displayed for EU distribution. See Apple's trader setup instructions.

Apple account ready: the membership is active, you can open your organization's App Store Connect account, and required account agreements are complete. Keep the renewal date with your organization's billing records.

3.3. Register a Google Play organization account

Use Google Play Console to publish on Google Play.

1. Sign in to Google Account with the account your organization will use as the permanent Play Console owner, or create one. Enable two-step verification and maintain recovery options. See Google's security setup instructions.
2. Open Play Console signup. Check the signed-in email before starting, especially if you also use a personal Google Account.
3. During registration, choose Organization as the developer account type. Complete the agreement and payment steps as prompted. The standard registration fee is US$25 once; prepaid cards are not accepted. See Google's registration instructions.
4. Link or create an organization Google payments profile. This profile holds the legal identity Google verifies. Use the publishing legal entity's name and address, matching its D-U-N-S record and documents; do not select an unrelated personal payments profile.
5. Enter the D-U-N-S number, organization website and phone number, contact person, and requested contact details. Choose the public developer name and public developer email and phone deliberately: Google displays the organization's legal name and address and its developer email and phone on Google Play. Google's private contact details are separate.
6. Open Play Console Home and work through the outstanding account verification tasks. Submit the requested identity and organization documents. Google's accepted documents vary by country; follow the list linked from the verification form.
7. Complete website verification using the steps below. For organization accounts, identity and website verification must be completed before phone verification can proceed.
8. Complete the email and phone verification prompts. Select Verify email address or Verify phone number, receive the code, and enter it with Verify. Use international phone format, for example +49…, and a number that can receive the offered text message or voice call.
9. Return to Home and confirm that all required account verifications are complete. Review the information under Developer account → About you and the public contact details before handing over to coapp.

See Google's developer identity verification instructions. A payment receipt alone does not mean the developer account is verified. Personal accounts have additional testing and device verification requirements; do not choose that account type as a shortcut for an organization.

3.4. Verify your organization website for Google Play

Google links your Play Console account to verified website ownership in Google Search Console. Ask your website administrator to help if you cannot manage the domain or website.

1. Open Google Search Console. If the website is already verified, identify its verified owner. Otherwise, add a property for your organization's website and follow Google's site ownership instructions. A domain property uses domain verification; a URL-prefix property offers the verification methods available for that website.
2. Complete Search Console ownership verification. Keep the verification record or file in place so ownership remains verified.
3. Return to Play Console Home and open the pending website verification task, or open Developer account → About you and the organization website details. Enter the matching website URL and send the website verification request from the account details form.
4. If the same Google Account owns the website in Search Console and the developer account, Google approves the association automatically. Otherwise, ask the verified website owner to approve the request received by email or in Search Console.
5. Wait for the confirmation email and Play Console Inbox message. Return to Home and check that the website verification task is complete.

A social media profile cannot serve as the website for this verification. If the request fails, check the URL and whether the verified owner approved it, then resend it. See Google's website verification instructions.

Google account ready: identity, website, and required contact checks are complete, and no account verification task blocks submission.

4. Create and retain ownership of the app records

An app record is the store entry for your app. Creating it does not publish the app. Agree the name, primary language, and app identifiers with coapp before creating records. Your organization’s account owner or administrator creates the records with coapp’s guidance before you grant app-specific access in step 5.

Choose your app name and identifiers

You choose your app's public name and its technical identifiers. Send your preferred values to coapp before registering the Apple identifier or uploading the first Android bundle. coapp checks their format and availability with you and uses your confirmed choices in the app.

Name or identifier	What it means	Example
Public app name	The name members recognize in the stores and on their device. Choose a clear name that matches your community's brand.	Example Community
Apple Bundle ID	The permanent technical identity of your iOS app. It is separate from the public name.	org.example.community
Android package name / application ID	The permanent technical identity of your Android app. It is set in the app bundle coapp prepares.	org.example.community
Apple SKU	Your internal tracking code in App Store Connect; members do not see it.	example-community-ios

For the Bundle ID and Android package name, use these naming practices:

• Start with a domain your organization owns, written in reverse order, then add a short, stable app name. For example.org, this could be org.example.community; for example.de, it could be de.example.community.
• Use lowercase ASCII letters and dots between parts. If you need digits, place them after the first letter of a part. Avoid spaces, umlauts, accented letters, hyphens, and other special characters. This conservative format works for both platforms; Android requires at least two parts, each beginning with a letter.
• Choose a distinct identifier for each separate app. You can use the same identifier for the iOS and Android versions of your community app when available in both stores.
• Keep the identifier stable. Leave out version numbers, launch years, employee names, and temporary campaign names. Keep it through future updates and public app-name changes.
• Replace the examples with your own domain and app name. Do not use coapp's domain or another organization's domain as your prefix.

For an existing app, send coapp its current identifiers and keep them for updates. Apple's Bundle ID cannot be changed in the app record after a build is uploaded. Google Play package names are unique and permanent; a different application ID identifies a different app, rather than an update. The Apple SKU also cannot be changed after record creation. See Apple's app identity fields, Android's identifier rules, and Google Play's package-name guidance.

Apple app record

1. Sign in to App Store Connect and select your organization.
2. Open Apps, select the + button at the top left, then choose New App.
3. Select iOS and enter your chosen name and primary language. Select your chosen Bundle ID, confirmed with coapp, and enter your SKU. If the Bundle ID is missing, your Account Holder or Admin must register it first as described below, then return to this form.
4. Choose the required User Access, select Create, and confirm that the record appears in Apps.

The Account Holder, Admin, or App Manager can create the record. If creation is blocked by an agreement, the Account Holder must accept it in Business. See Apple's app record instructions.

To register your chosen Bundle ID, the Account Holder or Admin opens Apple Developer Certificates, Identifiers & Profiles → Identifiers → +, selects App IDs, and continues to the App ID form. Enter a recognizable Description, choose Explicit App ID, and enter your chosen value in Bundle ID. Select the app capabilities confirmed with coapp, then choose Continue, review the details, and select Register. Use an explicit identifier for this app, rather than a wildcard. See Apple's App ID registration instructions.

Google Play app record

1. Sign in to Play Console and select your organization's developer account.
2. Open Home → Create app.
3. Enter the agreed app name and default language, choose App, and select the free or paid download option agreed with coapp. This choice concerns the store download price; it is separate from your community's membership fees.
4. Enter your member-support email, review the declarations and Play App Signing terms, and select Create app.
5. Confirm that you can open the new app's Dashboard. Send coapp your chosen Android package name before the first upload. This value is set in the app bundle; you do not enter it in the Create app form. coapp prepares and uploads the bundle with your confirmed identifier.

See Google's app setup instructions.

Do not transfer ownership of the accounts or app records to coapp. Keep the Account Holder or account-owner role with a permanent person in your organization.

5. Give coapp the required store access

Use support@coapp.io as the invitation email address for both developer accounts. Give coapp the access below to prepare, upload, test, submit, and publish new app versions and updates on your account holder’s behalf. Once your release approver has approved a version as described in step 11, coapp can submit it for store review and publish it after store approval without your account holder having to upload or release it personally. Keep account ownership with your organization and use separate user invitations. Do not share owner passwords, recovery codes, or two-factor codes.

Invite coapp to Apple

1. As the Account Holder or an authorized user manager, open App Store Connect Users and Access → People.
2. Select the + button at the top left, enter the coapp contact's name, and use support@coapp.io as the invitation email address.
3. Select App Manager. Leave Admin, access to reports, and Certificates, Identifiers & Profiles access unselected.
4. Select Next and give access only to your white-label app, then select Invite.
5. Ask coapp to accept the invitation and confirm access. Apple invitations expire after three days; resend an expired invitation if necessary.

App Manager lets coapp upload signed builds, manage TestFlight, submit versions for review, and publish approved versions for the assigned app. Developer can upload builds but cannot submit and publish versions, so App Manager is the minimum role for this release workflow. Apple also includes management of the assigned app's store information and pricing in that role; those permissions cannot be separated from the role. See Apple's role definitions, submission permissions, and publication permissions.

Signing setup is separate from publication access. Your organization's Account Holder or Admin handles the creation and renewal of distribution certificates and profiles with coapp so signed builds are available for upload. App Manager does not grant that certificate-management authority. Keep these account-wide tasks with your organization. If a specific signing task requires coapp to access Certificates, Identifiers & Profiles, agree the necessary access for that task and remove it afterward; Apple cannot limit that access to one app, and it makes all app information visible. See certificate permissions, distribution profile permissions, and user invitation instructions.

Invite coapp to Google Play

1. As the account owner or account administrator, open Play Console Users and permissions and start a new user invitation.
2. Enter support@coapp.io as the invitation email address. The invited user must sign in with that email.
3. Under App permissions, select Add app, choose your white-label app, and select Apply. Enable only the three release permissions below for that app.
4. Leave Account permissions and Admin (all permissions) unselected. Your organization's account owner or administrator creates the app record in step 4.
5. If you set an access expiry date, agree it with coapp so it covers the release and ongoing service. Select Invite user and ask coapp to confirm access.

App permission for ongoing releases	What coapp can do
View app information (read-only)	View the app and its release information.
Release apps to testing tracks	Upload app bundles and distribute test releases.
Release to production, exclude devices, and use Play App Signing	Submit and roll out production releases and updates, and use Play App Signing.

Testing access alone does not permit production publication. Google bundles device exclusion and unpublishing/republishing with production release access; these cannot be separated from that permission. With the permissions above, coapp can submit and publish new versions on your account holder’s behalf. Your release approver still provides the publication approval described in step 11.

Add any of the following app-level permissions only when coapp performs the corresponding task. Otherwise, your organization completes that task. Remove temporary permissions when the task is finished.

Permission for a specific task	When to add it
Edit and delete draft apps	coapp needs to edit the initial draft app.
Manage testing tracks and edit tester lists	coapp configures testing or manages tester lists.
Manage store presence	coapp updates store text, images, or distribution details. This also permits pricing and in-app product changes.
Manage policy declarations	coapp enters and submits policy and Data safety declarations approved by your organization.

See Google's permission definitions and invitation instructions.

Confirm the account handover

Send your coapp project contact the legal publisher name, Apple Team ID, Google developer account name, your chosen Apple Bundle ID and Android package name, links to the app records if already created, and confirmation that verification and invitations are complete. Include any outstanding account task and the person handling it. Your organization's account owner continues to handle payments, renewals, legal declarations, and owner-only agreements.

If account setup is blocked

Problem	Next step
D-U-N-S number or organization details are rejected	Check the exact legal entity and address in Dun & Bradstreet. Request corrections there and allow the store to receive them before retrying.
Apple enrollment is still pending	Check the enrollment status in your Apple Developer account and respond to requested evidence. Contact Apple Developer Support with the Enrollment ID if you need help.
Google phone verification is unavailable	Finish identity and website verification first, then retry from the account verification task.
Google documents are rejected	Check the accepted document types in the verification form and match the legal name and address to the payments profile.
coapp cannot see or update the app	Check the selected organization, invitation status, and any expiry date. At Apple, confirm the App Manager role and access to the white-label app. At Google, confirm the app is assigned with the three release permissions above. If signing is blocked, ask your organization’s Account Holder or Admin to check the signing setup with coapp.
You cannot access an existing owner account	Use the store's account recovery or support process before creating another account or app record.

Tell coapp about a blocker while you continue preparing branding and store information in the following steps. Account verification and app review are separate: a verified account still requires the app to pass store review.

6. Deliver the app identity and brand assets

Provide the final app name and confirm that your organization owns or licenses the name, trademarks, images, fonts, and other supplied artwork. Send approved master assets rather than screenshots or drafts. coapp derives the required platform, device, and store sizes from these files.

For the logo and app icon, provide:

• an editable vector master as SVG, Adobe Illustrator (.ai), or EPS, or the original shared Figma source; and
• your existing approved app icon, if available. For a prepared icon, use a square 1024 × 1024 px, sRGB PNG without baked-in rounded corners, small text, or fine details that become unclear at small sizes. If you only have the master logo, confirm the icon design with coapp before preparing additional files.

Confirm with coapp which additional files are needed before commissioning separate artwork. If coapp requests prepared Android icon files, provide:

• a transparent 1024 × 1024 px PNG for the adaptive-icon foreground;
• an approved six-digit hex color for the adaptive-icon background, or a separate background image when required; and
• a transparent, single-color 1024 × 1024 px PNG for the themed icon.

Keep essential artwork inside the central safe area described in the Android adaptive-icon guidance, because Android applies different icon masks.

For the splash screen, send your preferred logo and background color. If coapp requests prepared splash-screen files, provide:

• the editable vector logo and a centered, transparent 1024 × 1024 px PNG version;
• the background separately as a six-digit hex color; and
• optionally, a dark-mode splash logo and dark background color.

Do not send a precomposed phone-sized or full-screen splash image. Separate logo and background files adapt to different devices and aspect ratios. See the Expo app-icon and splash-screen guidance.

If you supply all these prepared files, you can use this delivery structure:

brand/
  logo-master.svg
  app-icon-1024.png
  android-foreground-1024.png
  android-monochrome-1024.png
  splash-logo-1024.png
  brand-colors.txt

Identify colors in brand-colors.txt with #RRGGBB values. Include the third line for a dark-mode variant:

icon-background: #RRGGBB
splash-background: #RRGGBB
splash-background-dark: #RRGGBB

7. Provide store assets, copy, and distribution choices

Your organization provides the store screenshots, descriptions, and keywords for the white-label app. Confirm the required screenshot formats and store text fields with coapp, then send final, approved information:

• app and store name;
• store screenshots;
• short and full store descriptions for every supported language;
• keywords where required by the store;
• countries or regions where the app should be available;
• intended target audience and any community content relevant to age ratings; and
• any other store listing information requested by coapp.

Name one person to approve the compiled store presentation. Incomplete or inconsistent information can delay submission or review.

8. Provide legal, privacy, and support information

Send working, publicly accessible URLs for your privacy policy, terms, and member support. Also provide accurate answers about the app's content, target audience, data use, and distribution. Review them with your legal or privacy contact.

You can reuse your community's existing legal pages if they contain the information required for your app. coapp already hosts configured community policies at https://your-community-domain/legal/privacy-policy and https://your-community-domain/legal/terms-and-conditions. Replace the example domain with your community's domain and check that the pages load without signing in and contain current, approved text. See Manage your community's legal information. Your organization supplies and approves the legal content.

Ask coapp for the technical data-handling information needed for Apple's app privacy and Google's Data safety declarations. Your legal or privacy contact reviews it together with your community's own data use and retention practices; do not guess technical answers.

coapp already provides an option for members to delete their community account inside the app. You do not need to implement an additional in-app account-deletion feature for your white-label app.

Google Play also requires a working web link where members can request account deletion without reinstalling the app. Your community's existing web account-deletion flow can meet this requirement; you do not necessarily need a separate page or form. Members can sign in to the community web app and delete their account there. See Delete your community account.

Confirm the URL with coapp before submission and enter it in Google Play Console's Data safety form. Check the link while signed out: it must provide a clear route to deletion, including any sign-in step, and identify your app or the developer name from the store listing. A generic login page without clear deletion guidance may be insufficient. Explain any membership or administrator-role restrictions and provide a support contact for members who cannot complete deletion themselves. State which associated data is deleted and explain any retained data, including the reason and retention period.

Review the current Apple App Review Guidelines and Google Play account-deletion requirements with your legal or privacy contact.

9. Confirm the community and registration flow

The app uses your existing community and its registration settings. You do not need to create another community or implement a separate registration process. Send coapp:

• the community that the app must open;
• the supported app languages; and
• your community's current registration method and any intended changes.

Autonomous registration lets a new member complete a simple, free registration in the app. Paid registration, invitation-based registration, and registration with custom fields continue through the community's web registration flow. If needed, review Configure how people join your community.

10. Prepare representative content and review access

Make sure the community contains current, representative content that lets Apple and Google understand the member experience. Do not rely on empty sections or unfinished placeholders.

Use a dedicated, reusable Community Account with access to the relevant app features for store review. An existing review account can be reused if its access is still suitable; create one only if needed. Give coapp the login details through the agreed secure exchange method, clear sign-in instructions, steps for reaching important functions, and a contact who can quickly resolve access problems. Keep the account active throughout review.

Apple and Google require working access for restricted or signed-in content. See Apple's review guidance and Google Play's sign-in requirements for review.

11. Review and approve the prepared app

When coapp provides the prepared app identity and store presentation, check:

• app name and publisher name;
• icon, splash screen, colors, screenshots, and store copy;
• languages and distribution regions;
• privacy, support, and deletion links; and
• the community, registration flow, and review account.

Send one consolidated set of corrections. The named release approver should confirm in writing when the app is ready for submission.

12. Support submission and store review

After approval, coapp coordinates the technical submission in your organization's app records. Monitor messages from Apple, Google, and coapp. Your store account owner must complete any outstanding agreements, declarations, or account actions.

If a store asks a policy, content, legal, or business question, provide an approved answer promptly. If it rejects the submission, coapp coordinates the technical changes while your organization supplies any required account changes, content, evidence, or policy clarification.

Apple and Google make the final review decision. Neither coapp nor your organization can guarantee approval or a particular publication date.

13. Publish and operate the app

Confirm the release timing with coapp after store approval. When the app is available:

1. Open both store listings and verify the published name, artwork, text, links, and supported regions.
2. Share the official store links with members.
3. Tell members which email address to use to sign in and where to request support.
4. Keep store memberships, organization details, agreements, legal URLs, and the review account current.
5. Notify coapp before changing store access or when brand, legal, registration, or distribution information must change.

Your organization remains responsible for member support, moderation, legal compliance, and privacy requests. coapp maintains the technical release process and coordinates future technical app updates as part of the agreed service.

Related articles

• Request a white-label mobile app
• Configure how people join your community
• Download and use the coapp mobile app