OpusBUSINESS EXPERT

Your app's icon carries your brand. The App Store says the seller is your developer

Andy Shepherd7 min read

The app was built three or four years ago. It works, it carries your logo on the icon, and nobody has needed to think about it since.

Open its page on the store and read the small line under the name, the one that says who is selling it. In a lot of small firms that line is not the company. It is a person, with a surname, and usually it is whoever built the thing.

That line is not decoration. It names the account the app is published from, and for every practical purpose the account is the app.

Why a person's name ends up there

Apple's own account help is blunt about this. Enrol as an individual or a sole trader and your personal legal name is what appears as the seller, and its instruction is not to put an alias, a nickname or a company name in the name fields. There is no setting that hangs a trading name on an individual account.

So when a developer builds an app on the account they already hold, this is the result. Not deception, in almost every case: it was the quickest route on the day, in exactly the way your domain ended up registered in your web designer's name.

The difference is that a domain can be transferred with a fortnight of paperwork. An account cannot be renamed at all.

Moving it later is not a setting you flip

To publish under the company's name, the company needs its own organisation account. Apple's requirements for one are a short list that takes longer than you would expect.

  1. 01The company has to be a legal entity. Trading names, fictitious businesses and branches of something else are not accepted
  2. 02It needs a D-U-N-S number, the nine-digit business identifier issued by Dun & Bradstreet. Free in most places, and not instant
  3. 03Whoever enrols must have authority to bind the company to an agreement, and may be asked for a reference who can confirm they do
  4. 04The email address has to be on the company's own domain, and that domain needs a working public website on it. A registrar holding page will not do

An individual account cannot be promoted to an organisation one by ticking something either. Apple's documentation says to contact them about it.

None of this is difficult. All of it is slow, and all of it is considerably slower during a falling-out than before one. The useful moment to ask whose account an app will live in is while you are still reading the quote.

The renewal nobody has diarised

Membership is annual. Apple's page puts the Developer Program at 99 US dollars a year, charged in local currency where that is available, and an enrolment made through the Developer app renews as a subscription until somebody cancels it.

Which means it can lapse: on a card that expired, or in the mailbox of a developer who has moved on. Apple is precise about what happens next.

If your Apple Developer Program membership expires, your apps will no longer be available for download and you won't be able to submit new apps or updates or access Certificates, Identifiers & Profiles. However, your apps will still function for users who have already installed or downloaded them.

Apple's account help, on expired memberships

A second detail from the same page matters more than it looks. Renewal has to be done by the Account Holder. If that role sits with your developer, nobody in your business can renew the membership, however willing they are and however obviously it needs paying.

It is recoverable, to be fair to Apple. Renew late and free apps come back within about a day, and nothing has to be resubmitted. The hard part is noticing, because the warnings go to whoever holds the account.

The membership belongs on the same short list as the domain, the hosting and the certificate: small annual payments, each quietly holding up something the business depends on, none of them big enough for anyone to have written down.

The deadline that takes your app off new phones

This is the part nobody raises at the quote stage.

A store sets a floor for how recent an app's build has to be, and the floor moves every year. Google documents its version plainly, which is why it is the example here.

Google's current rule runs from 31 August 2026. A new phone app or an update to one has to target Android 16 to be accepted at all. An existing app has to target Android 15 or higher to stay available to new users on devices running a newer version of Android than the app itself targets. Below that line, the app is offered only to devices running the same or an older version of Android.

Read that from a customer's end. The app has not been removed and it has not been rejected. It is still there, still installed and still working on every phone that already has it, which is why nobody inside the firm sees anything wrong. It has simply stopped being installable by the people most likely to be looking for it, because their phone is newer than the app.

Which is the same shape as the expired membership above. Neither sends anybody a letter, and both leave the app working for everyone who already has it. A failure nobody in the business can see is one that needs a date in a diary rather than somebody's attention.

Apple answers the question itself

This is worth having to hand before the next conversation with a developer, because it settles the argument without anybody needing to be difficult. Apple's account help has a section for precisely this arrangement, where a firm hires somebody to build an app on its behalf:

The organization should enroll in the Apple Developer Program using the steps outlined above. They should add you to their development team in their account on the developer website so you can access membership resources.

Apple's account help, on contract developers

The firm holds the account. The developer is added to its team and gets what they need to do the work. The company's name is then what the store shows as the seller. That is the platform describing the ordinary arrangement, not an awkward demand to make of a supplier.

What to get in writing

Three questions, and they fit in one email before anybody signs anything.

  1. 01Whose account will the app be published from, and whose name will the store show as the seller
  2. 02Who pays the annual membership, and who receives the renewal notices
  3. 03Who is responsible for keeping the app above each platform's minimum build every year, and whether that work sits inside the price or is quoted separately

The third gets skipped, because at the point of signing an app looks like a project with an end date. It is not. It is a small permanent obligation sitting in somebody's calendar, and all that is undecided is whose.

We are the firm this gets asked of

We hold our own developer accounts, pay our own renewals and do the version work every year: the two apps for our sister practice, Opus PM and Opus Clients, and the rest of what we publish on the App Store, the Mac App Store and Google Play. So none of the above is a warning about app developers. It is a description of what holding an account involves, from a firm that holds them.

It is also why we would rather a client's app sat in a client's own account. A supplier holding the account has a client who cannot leave, which is a thin substitute for a client who does not want to.

If you have an app and cannot say which account it is published from, its store page answers half of that in about ten seconds. Ask us to work out the rest. The good outcome here is the same as it is with a domain: we tell you it is already in your name.


We work with businesses across Knutsford, Alderley Edge, Wilmslow, Altrincham, Stockport and Warrington, and remotely for clients anywhere in the UK.

If any of this sounds like your business, we will tell you plainly whether we can help.

We would like to use analytics cookies to understand how this site is used, advertising cookies to measure our ads, and to load our office map from Google. None of them loads on its own unless you accept — though Google Tag Manager itself loads either way, with every category switched off. The map also has a button of its own. Read our cookie policy