Guidelines 4.3(a) and 4.2.6: Publishing separate apps for multiple companies under one or separate developer accounts

Hello everyone,

I’m developing a work management app using React Native/Expo for multiple companies. The apps share a common codebase and similar core functionality, but each company has its own app name, logo, bundle ID, and company-specific data.

Each company wants a separate app publicly available on the App Store so users can search for and download it. Private distribution through Custom Apps or a single shared app with a company selector would not meet their requirements.

I’d like to understand how App Review Guidelines 4.3(a) and 4.2.6 apply to these two scenarios:

1. All apps published under one organization’s developer account

Our company would develop and publish all client apps under our own Apple Developer Program organization account. Is there a compliant way to support this model? What requirements would each app need to meet?

2. Each app published under the client company’s own developer account

Each client company would enroll in the Apple Developer Program and publish its app under its own organization account, while our team handles development and assists with submission. Could these apps still be rejected under Guideline 4.3(a) because they share a codebase and similar functionality?

For both scenarios, I’d appreciate clarification on the following:

  • What differences in functionality, content, or business workflows would help establish each app as a distinct product?
  • How does Guideline 4.2.6 apply to this shared-platform model?
  • What supporting documentation should we provide, such as development contracts or letters of authorization?
  • How should we explain the business need for separate apps in App Review Notes?

Has anyone successfully implemented a similar model? I’m looking for a compliant, sustainable approach, rather than a workaround to the review guidelines.

Thank you for your advice and experience.

4.2.6 answers most of this. Apps made from a shared template have to be submitted by the business whose content they carry, from that business's own developer account. So your scenario 2 is the compliant one and scenario 1 is the one that gets rejected. Each client enrols as an organization (it needs a D-U-N-S number, which can take a couple of weeks) and adds your team in App Store Connect as Admin or App Manager. A shared codebase is fine under that model. What review checks is that each app plainly belongs to that company: its own name, branding, data and sign-in, plus a demo login with realistic company data. In Review Notes, one line covers the relationship: "Built by [your company] for [client], published on [client]'s own account." Keep a short authorization letter from each client ready in case review asks for one.

If one of them gets rejected and you'd rather hand it off, I do fixed-price fixes for this: https://native-wrap.kiwitechlab.net