How to Build a Shopify App: Scaffolding to Distribution
A practical walkthrough of how to build a Shopify app: CLI vs. Dev Dashboard, what an app is made of, testing it, and custom vs. public distribution.
Learning how to build a Shopify app starts with picking one of two starting points: a CLI-scaffolded React Router app for anything with server-side logic, or a Dev Dashboard app for a simple API integration with no UI. From there, you choose custom or public distribution before you ship — a decision Shopify says can't be changed later.
Pick Your Starting Point: Shopify CLI vs. the Dev Dashboard
Shopify gives you two genuinely different paths into app development, and picking the wrong one means redoing setup work later. Running `shopify app init` scaffolds a React Router app, which Shopify currently recommends as the template for most apps that need server-side logic. If you're building a simple custom-distribution app that doesn't need server logic at all, there's also an extension-only template built around an App Home UI extension.
The second path skips the CLI scaffold entirely. For a simple integration — one that only needs API credentials and has no embedded UI — Shopify recommends creating the app directly in the Dev Dashboard instead. The Dev Dashboard is explicitly positioned as the simplified interface for quick integrations, like connecting an existing system to Shopify, while anything headed for the App Store should be built with Shopify CLI from the start.
Before you scaffold with the CLI, you need app-development permissions, a dev store (you can create one with `shopify store create dev`), the latest version of Shopify CLI, and the latest Chrome or Firefox.
What a Shopify App Is Actually Made Of
Whichever path you start from, a Shopify app is built from the same handful of components, and only one of them is yours to host.
Authentication gets your app an access token for whatever scopes a merchant grants it — the scaffolded React Router app handles this automatically, so there's no manual OAuth flow to write before you can call the GraphQL Admin API. Extensions are the UI pieces that render inside Shopify's own surfaces, built from Polaris web components, Shopify's design system for app interfaces. Functions run custom logic in Shopify's own request path, hosted by Shopify rather than your servers. And custom data — anything Shopify's built-in model doesn't cover — lives in metafields and metaobjects. Events and webhooks notify your app when something changes in the store, so it doesn't need to poll for updates.
The practical upshot is that your own backend is the only piece you self-host; Shopify hosts the extensions and Functions that run inside its surfaces. That's a meaningfully smaller footprint than building a fully self-hosted integration, which is part of why a Dev Dashboard app with no UI can be a reasonable starting point for connecting an existing system without taking on a full app build — the kind of work our shopify app development service scopes and builds end-to-end when it goes beyond a weekend project.
Running and Testing It on a Dev Store
Once your app is scaffolded, `shopify app dev` starts a local development server and does three things behind the scenes: it creates a Prisma SQLite database for session storage, and it opens a Cloudflare tunnel between your local machine and your dev store, so Shopify can reach your locally running code over HTTPS.
With the dev server running, pressing `p` opens your app's install URL in a browser. Installing it gives you a working dev store with your app attached, and the sample app includes a "Generate a product" action that seeds a test product — a quick way to confirm the app can actually talk to the store before you build anything further.
If you went the Dev Dashboard route instead, testing looks a little different: an app needs at least one released version — covering its app URL, webhooks API version, and requested scopes — before any store can install it. It's also worth knowing that scopes you add in a later version aren't automatically applied to stores that already installed the app; merchants have to manually approve the new scopes themselves. For an app used only within your own organization, a client-credentials grant — your Client ID and Client secret — issues an access token that expires after 24 hours, which is enough for internal integration work without building a full OAuth flow.
Custom App vs. Public App Store App
This is the decision Shopify is explicit about not letting you undo, so it's worth getting right before you write much code.
Custom distribution needs no approval from Shopify at all. It installs on a single store, on multiple stores inside the same Plus organization, or on dev stores — but it can't charge merchants through Shopify's own app billing system, so any monetization has to happen outside Shopify. Public distribution is the opposite trade: your app can be installed on any Shopify store, but it has to clear Shopify's review process first, and you need to register for the Shopify App Store, which carries a one-time fee.
If you're building something for one client or for your own operations, custom distribution is almost always the right call — it's faster to ship and skips the review cycle entirely. If you're building a product meant to reach many merchants, public distribution is the only path that gets you there, but budget time for Shopify's review and design requirements before you plan a launch date around it. Once your app is built and ready to submit, running it against Shopify's own review expectations ahead of time — the same checks our breakdown of what Shopify's AI self-review actually checks covers — can save you a full review cycle versus finding out about an issue after you submit.
If you've built Shopify apps before and remember "private apps" as a third option, that path no longer exists: private apps were deprecated as of January 2022, and every remaining one was automatically migrated to a custom app by January 20, 2023. Today it's just the two distribution types above. Theme app extensions also carry a fixed constraint worth knowing regardless of which distribution you choose: a 100 KB Liquid size limit, though custom-distribution apps and apps with Built for Shopify status can request an exception to it.
Whichever distribution path you pick, pricing and store requirements are worth scoping early too, which our guide to Shopify App Pricing's new store requirements walks through in more detail.
If you want help scoping or building your Shopify app from the ground up, talk to our team.
Frequently asked questions
Do I need to code to build a Shopify app?
Yes, for both documented paths. A CLI-scaffolded React Router app is a coding project with server-side logic, extensions, and API calls. A Dev Dashboard app needs less code — it's meant for simple integrations that just need API credentials — but you still need to write the code that calls Shopify's APIs with the access token it issues.
What's the real difference between a custom app and a public Shopify App Store app?
A custom app installs on a single store, a Plus organization's stores, or dev stores, needs no Shopify approval, and can't bill merchants through Shopify's billing system. A public app can be installed on any Shopify store but must pass Shopify's review and requires registering for the App Store for a one-time fee. You can't switch between the two after choosing.
What tools do I need before I start building a Shopify app?
For the CLI path: app-development permissions, a dev store, the latest Shopify CLI, and the latest Chrome or Firefox. For the Dev Dashboard path, you mainly need app-development permissions and a dev store to install the app on for testing.
Can I build a Shopify app without the Shopify CLI?
Yes. For a simple integration that only needs API credentials and no embedded UI, Shopify recommends creating the app directly in the Dev Dashboard instead of scaffolding it with the CLI. Apps meant for the Shopify App Store, though, should be built with the CLI.