
If you are comparing a Shopify custom app vs public app vs private app, the first thing to know is that the words have moved under your feet. Half the articles you will find still describe a setup Shopify no longer offers. This page is for store owners and project leads who need the current meaning of each term, what changed and when, and how to pick the right type before paying anyone to build it.
The short answer
Today Shopify documents two kinds of app: public and custom. “Private app” is an old name that survives in tutorials, agency pitches and older integrations. A third label, “legacy custom app”, covers custom apps created in the store admin before 1 January 2026.
| Term | Current status | Who can install it | Review by Shopify |
|---|---|---|---|
| Public app | Current | Anyone, from the App Store (listed) or by link (unlisted) | Yes |
| Custom app | Current | One store, or stores in one Plus organisation | No App Store review |
| Legacy custom app | Existing apps keep working; new ones cannot be made this way | The store it was created on | No |
| Private app | Old name, not in Shopify’s current app-type list | Store it was created on | No |
The rest of this article unpacks each row and the parts that trip people up.
What Shopify’s own documentation says
Shopify’s help centre describes two app types: public apps, which are either listed or unlisted and both go through Shopify’s review, and custom apps, which are built for one store and managed in the Dev Dashboard. An unlisted public app does not appear in App Store search or categories, so you install it from a link or the developer’s site.
The same page defines legacy custom apps as those created before 1 January 2026, managed from the Shopify admin. A Shopify developer community announcement states that from that date you cannot create new legacy custom apps, that existing ones are not affected, and that new apps should be made in the Dev Dashboard.
Public apps
A public app is built to be installed by many merchants. The developer lists it, submits it for review, and usually charges through Shopify’s billing. Shopify’s app requirements checklist gives a flavour of the review: a setup screencast, test credentials if you integrate with third-party platforms, a privacy policy, and a limit on how far the app may reduce storefront performance scores.
Pick a public app when a mature product already does the job. You get updates, support and a monthly fee instead of a build bill. The catch is that you take the product as it is. If it does 80 per cent of what you need, the remaining 20 per cent is yours to patch by hand.
Custom apps
A custom app is built for your business. Shopify’s distribution guide calls this custom distribution: you generate an install link and send it to the store owner. It can be installed on one store, or on several stores in the same Plus organisation, and the choice cannot be changed once made. There is no App Store listing and no App Store review.
Two practical points:
- Creation happens in the Dev Dashboard. Shopify’s help page says custom apps are managed there, with logs and health metrics and room to test on development stores. People need the App developer role, or the Build and manage apps organisation permission on Plus. Collaborators cannot open the Dev Dashboard, so decide early whose account owns the app.
- Tokens work differently. Shopify’s access token docs describe several grants. For a server-side integration that acts only on stores in your own organisation, the client credentials grant gives a token that lasts 24 hours, and the app requests a new one when needed. The older admin-made kind had a token Shopify generated at install, which is no longer how new apps work.
For the build side, see the step-by-step custom app guide.
Legacy custom apps
If your store already has apps under Settings, Apps, Develop apps, those are legacy custom apps. They keep working and you manage them from the admin. Shopify’s help page notes that the “App development > Develop” store permission applies only to them.
Two cautions. First, Shopify releases a new API version every three months and each stays usable for a year; after a breaking change, developers have nine months to update before the app becomes unsupported. A legacy app nobody maintains will eventually hit that wall. Second, the help page says unsupported apps raise a warning in the admin, and that you can contact the developer, hire a Shopify Partner, or delete an app you no longer use.
Private apps: what the term means now
“Private app” was the pre-2022 name for a store-only app that authenticated with an API key and password. Secondary sources, such as developer forums, report that Shopify retired private apps in early 2022 in favour of custom apps that use access tokens in a request header. I could not find that spelled out on a current Shopify documentation page, and Shopify’s present app-type list does not include the term. Treat it as history.
Why it still matters: agencies and tutorials use “private” as a casual word for “not in the App Store”. If a quote says private app, ask what they actually mean: a Dev Dashboard app with custom distribution, an existing legacy custom app, or an unlisted public app. Each has different ownership, token handling and review consequences.
How to choose
Ask these in order:
- Does a public app already do it? Check the App Store, and check Shopify Flow for simple rules.
- Will more than one business use it? If you plan to sell or share it, a public app is the route, and review is part of the job.
- Is it only for your store (or Plus organisation)? Then custom distribution.
- Do you already have a legacy custom app? Keep it running, but give it an owner and a review date, and build new work in the Dev Dashboard.
Our overview of when you need a custom app adds a decision table, and third-party app bloat covers the opposite problem of too many public apps.
Frequently Asked Questions
Is a private app the same as a custom app?
Not exactly. Private apps were the older mechanism; custom apps replaced them. People use the terms loosely, so confirm which one is being described.
Can I still create a legacy custom app in my Shopify admin?
According to Shopify’s developer community announcement, no. From 1 January 2026 new ones cannot be created there. Existing ones are unaffected.
Does a custom app need Shopify review?
Custom distribution has no App Store review. Public apps, listed or unlisted, do. Some extension types may still need Shopify approval before release.
Can I turn a custom app into a public app?
Shopify says you cannot change the distribution method after you select it. Going public would normally mean a new app and a review.
Which type is cheapest?
A public app is usually the cheapest to start, because you pay a subscription instead of a build. A custom app costs more up front and has running costs; see our guide to custom app cost drivers.
Conclusion
The cleanest way to think about a Shopify custom app vs public app vs private app question is to drop “private” from your vocabulary and ask two things: who will use it, and who will maintain it. Many people for a common feature means public; one business with unusual rules means custom, built in the Dev Dashboard. If you would like help with this, CYPHEX can plan and deliver it for you, with one project lead as your contact. See also our Shopify app development service.
Stock photography provided by Pexels under the Pexels License.
