Skip to main content

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.

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.

For Apple, enroll the legal entity that should appear as the seller, or verify that its existing Apple Developer Program membership is active. The Account Holder must accept agreements and maintain the membership. See Apple Developer Program enrollment and Apple account roles.

For Google Play, create or verify an organization account using the legal organization's details and complete Google's verification. See Google Play organization-account requirements and developer account types.

Confirm that the publisher name, address, contacts, tax details, and payment information are current. Your organization pays all enrollment, registration, and other store fees and accepts or renews required agreements.

4. Create and retain ownership of the app records​

Create the iOS app record in App Store Connect and the Android app record in Google Play Console with the app identity agreed with coapp. If coapp coordinates this step with you, make sure the records are still created in your organization's accounts.

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​

Invite the coapp contact as a separate user in each store account. Grant only the roles and app access that the coapp team requests for preparing and submitting the technical release.

Do not share the Account Holder's password or another person's login. Review Apple's role definitions and Google Play user permissions. Tell coapp when both invitations have been accepted and the required app records are visible.

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
  • a final 1024 × 1024 px, sRGB PNG app icon. It must be square, without baked-in rounded corners, small text, or fine details that become unclear at small sizes.

For Android, also 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, 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.

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 copy and distribution choices​

Send final, approved information rather than placeholders:

  • app and store name;
  • short and full store descriptions for every supported language;
  • countries or regions where the app should be available;
  • intended target audience and age-rating answers; 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.

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

Apple requires a privacy-policy link and an in-app account-deletion option when an app supports account creation. Google Play also requires an in-app deletion path and a working web resource for deletion requests. Review the current Apple App Review Guidelines and Google Play account-deletion requirements.

9. Confirm the community and registration flow​

Confirm with coapp:

  • the community that the app must open;
  • the supported app languages; and
  • whether your community allows autonomous registration.

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.

Create a reusable review account with access to the relevant app features. 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.