If a supplier builds your university’s app from a product it sells to other universities, Apple expects the app to be published from your developer account, not the supplier’s. That is guideline 4.2.6 of Apple’s App Review Guidelines, and it shapes how a branded campus app is set up, who owns its store listing and what you need before launch.

What the guideline says

Guideline 4.2.6, in the version Apple last updated on 16 October 2026, says apps “created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content”. It goes on: these services “should not submit apps on behalf of their clients”.

It allows one other route: a template provider can “create a single binary to host all client content in an aggregated or ‘picker’ model”, one app with a separate entry for each client. For a campus app, that would be a single app in which students pick their university.

Two more guidelines point the same way. Guideline 5.2.1 says apps “should be submitted by the person or legal entity that owns or has licensed the intellectual property and other relevant rights”. Guideline 4.3(a) suggests that an app with “different versions for specific locations, sports teams, universities, etc.” consider a single app. How they combine for a given app is App Review’s call.

What it means for a university

For an app that carries your name and crest, the content is yours, so the app goes out from your account. In practice:

  • Your university is the seller on the App Store listing, not the supplier.
  • The listing stays with you. The app record, its reviews and its ratings sit in your account, so changing supplier does not mean starting a new listing.
  • You need an Apple developer account for the university, if you do not already have one.

Setting up the Apple account

Apple’s enrolment page asks for four things: a legal entity that can sign contracts with Apple (it does not accept trade names or branches), a D-U-N-S number, a person with the legal authority to bind the organisation, and a public website on a domain associated with it.

The fee is 99 US dollars a year, with local prices shown during enrolment. Apple waives it for an accredited educational institution that has not signed the Paid Applications Agreement and does not sell digital goods or services through any of its apps. Apple Education UK’s onboarding kit puts it plainly: “As an accredited educational institution, you can join the Apple Developer Programme for free by applying online.” Eligibility is confirmed again at each annual renewal.

Letting the supplier work inside your account

You do not hand over your account to get the app built. In App Store Connect, an Account Holder, Admin or App Manager can add users. An App Manager “manages all aspects of an app, such as pricing, App Store information, and app development and delivery”, and can submit it for review, so adding your supplier as an App Manager for your app is enough.

Google Play

We found no Google Play rule like 4.2.6, but two policies matter. Its spam policy warns against “multiple apps with highly similar functionality, content and user experience”, and its impersonation policy says not to “imply that your app is related to or authorised by someone when it isn’t”. An app published from the university’s own account avoids both questions.

A Google Play account for an organisation needs a D-U-N-S number, which Dun & Bradstreet issues free, and a one-off registration fee of 25 US dollars.

A checklist

  1. Find out whether your university already has Apple and Google developer accounts, and who the Account Holder is.
  2. If not, find your D-U-N-S number or apply for one, and choose who will enrol with the authority to sign.
  3. Apply for Apple’s fee waiver if you have not signed Apple’s Paid Applications Agreement and none of your apps will sell digital goods or services.
  4. Add your supplier as an App Manager in App Store Connect and as a user with access to the app in Google Play Console.
  5. Agree who writes the store listing, the privacy details and the accessibility statement.

How Varsio does it

A Varsio app is published under your university’s name on iPhone and Android from your App Store account, and it can be live in 2 to 4 weeks from the day we have that account, sign-in access and the connections we agree for your pilot. How long a launch takes has the steps.