Shopify App Development Cost in 2026: Custom vs Public Apps, Revenue Share and Real Build Ranges

Shopify app development cost at a glance

This page is about building apps that extend Shopify: admin tools, sync jobs, checkout logic, storefront widgets. If you need the store itself, our Shopify website development cost guide covers themes, plans and store builds.

The first question decides most of the budget: is the app for your store, or for every store?

Ranges assume a team with a developer, QA and someone who owns scope. A freelancer can ship a small custom app for $2,000–$6,000. That works when the logic is simple and the developer stays around for API upgrades.

Custom app vs public app: why the same feature costs twice as much

Shopify has two ways to distribute an app. A custom app is installed on one store, or on stores in one Plus organization, through a custom distribution link. A public app can be installed by any merchant, either unlisted or through the Shopify App Store. The feature can be identical. The surrounding work is not.

One 2026 change matters for anyone budgeting a custom app: since January 1, 2026, merchants can no longer create new apps through the "Develop apps" screen in the store admin. New custom apps are created in Shopify's Dev Dashboard or with Shopify CLI, with versioned configuration for scopes, URLs and webhooks. Existing legacy apps keep working. In practice, this makes a "quick admin API token" setup a small development task rather than a five-minute click, and it's the right moment to put the app in version control.

What a public app adds, and why each piece is mandatory:

• Multi-store installation. OAuth with token exchange, per-shop sessions, scopes requested only when needed, and clean behavior on uninstall and reinstall.
• Billing. Apps sold through the App Store must charge through Shopify (the Billing API or Shopify's managed pricing). Free trials, plan changes, usage charges and proration all need code and testing.
• Privacy webhooks. Every public app must handle Shopify's mandatory compliance webhooks for customer data requests, customer redaction and shop redaction. If you store customer data, deletion has to actually work.
• Onboarding and settings. The merchant installs the app without you on a call. The first screen has to explain itself.
• Listing and review. Screenshots, a demo video or screencast, a test account, and fixes after the reviewer's first round.

What Shopify takes from app sales in 2026

Shopify's revenue share terms changed on January 1, 2025, and they still apply in 2026. According to Shopify's developer documentation:

• $19 once to register a Partner account for the revenue share plan.
• 0% revenue share on the first $1M in lifetime gross app revenue, counted across all your apps and associated developer accounts. This replaced the older rule, which reset the $1M threshold every year.
• 15% on revenue above $1M, for developers earning under $20M a year.
• 15% on everything for developers above $20M in annual app revenue or companies with more than $100M in total revenue.
• 2.9% processing fee on all app billing, charged separately and regardless of the threshold, plus applicable sales tax.

Compared with mobile stores, that's generous early on. Apple takes 15% from day one under its Small Business Program, and Google Play's US terms since June 30, 2026 start at 10% on the first $1M. On Shopify, a new app pays only the 2.9% processing fee until it crosses $1M in lifetime sales.

The math that matters more for most new apps is the other side: how long it takes to earn back the build. A $60,000 app at an average of $25 a month per merchant needs 200 paying stores for a year just to recover the build, before support, hosting and marketing. Many App Store apps never reach that. If your business case depends on App Store sales, budget for marketing and support as seriously as for development, and see our SaaS development cost guide for the product side of that math.

The technical cost drivers specific to Shopify

Shopify app development cost calculator

Pick the distribution model, the surfaces the app touches and how much data it moves. The model uses planning hours from real estimates, adds 30% for QA and project management, and applies the rate you choose. It also estimates the monthly run cost and yearly upkeep.

Two patterns show up when you try it. Moving the same app from "custom, one store" to "App Store" adds 250–400 hours before any feature changes. And on custom apps, integrations dominate: one ERP sync often costs more than the entire admin UI.

Where the money goes in a public app

Rates by region, compared fairly

Same public app, the one from the chart above (about 1,100 hours with QA): midpoint build cost by team location.

• US onshore: full overlap with your team and easy live product sessions. Highest cost per hour.
• Latin America: what US buyers call nearshore, with most of the working day shared. Rates close to Central Europe. Our nearshore rates guide has per-country numbers.
• Central & Eastern Europe (Gilzor works from Poland and Cyprus): offshore for the US, with about 2–4 shared hours with the East Coast on a shifted schedule and little with the West Coast. App work fits that well: specs, staging stores and recorded demos carry most of the communication.
• South and Southeast Asia: lowest rates, widest spread in quality. Budget more of your own time for review, especially before the App Store submission.

For hourly rates by role across all app work, see app development cost per hour.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Should you build an app at all?

Six questions. The result tells you whether to build a custom app, a public app, or skip development and configure what exists.

App Store submission readiness

The review is where public app timelines slip. Shopify has published a target of roughly 8–10 business days for a first review, and developers in Shopify's community commonly report 7–14 business days, longer when fixes are needed. Most first submissions come back at least once. Tick what's already true for your app.

Hidden costs: what you pay after launch

What we see in estimates and first calls

• "It's a simple app" usually means a simple screen on top of a hard sync. The admin page takes a week. Deciding which system owns stock, price and order status, and what happens when the ERP is down, takes longer. We ask that per field before we estimate. Our API integration cost guide covers the general math.
• Public apps get scoped like custom apps. Founders budget the feature and forget billing, onboarding, privacy webhooks, listing assets and support tooling. That's where a $30,000 plan becomes a $55,000 invoice.
• Rate limits show up in production, not in demos. A development store with 50 products never throttles. A merchant with 80,000 variants on a standard plan does, on day one. We test with realistic data volumes before launch.
• Inherited apps are often stuck on old API versions. When we pick up an app from another team, the first job is frequently a forced upgrade with a deadline. Our tech troubleshooting work often starts there.
• Overruns come from unwritten scope. The Standish Group's CHAOS 2020 report classed only about 31% of software projects as successful on time, budget and scope. Shopify apps are small projects, but the cause is the same: edge cases that nobody wrote down until the reviewer or the first big merchant found them.

How to reduce the cost without breaking the app

1. Check Shopify Flow and existing apps firstMany "we need an app" requests are a Flow automation plus one existing app. Build only the part nothing covers.
2. Start as a custom or unlisted appShip to your own store or three pilot merchants. Add billing, listing and review when the feature is proven.
3. Use Functions and extensions instead of serversDiscount, shipping and validation logic that runs inside Shopify needs no hosting, scales with Shopify and avoids most rate-limit work.
4. Stay inside PolarisShopify's components cover settings, lists, forms and most dashboards. Custom design inside the admin costs more and reviews worse.
5. Write the data spec before quotesRecords, volumes, sync direction and the owner of each field. Vendors stop padding for uncertainty. For larger apps, a short business analysis phase does this properly.
6. Pick the team region for how you workIf your team works from tickets and async demos, an offshore team saves 50–75% against US rates. If you need daily live sessions, the overlap is worth paying for.

FAQ

Where Gilzor fits

We build custom Shopify apps, integrations and extensions as part of our web development work, with QA on the same team. Only 5% of the tasks we send to QA come back to developers; that's our own metric. For US clients, we work from Poland and Cyprus with a few shared hours on East Coast time and written, async-first reporting. If your app is one piece of a bigger product, our web application development cost guide covers the rest.

Send us the workflow, the data volumes and any quote you already have. We'll tell you whether it should be an app at all, and which kind.