Most Shopify app developers make very little, a solid middle earns $2,000 to $20,000 in MRR, and a small top tier makes far more: app revenue follows a power law. Shopify takes 0% of your first $1 million and 15% after. Here are the real numbers, costs included.
The Revenue Share Math First
Start with the platform's cut, because it shapes everything downstream. Under Shopify's revenue share terms, developers pay 0% on their first $1 million USD of gross app revenue and 15% above that. Two details matter more than the headline:
The exemption is now lifetime, not annual. Until mid-2025, the $1 million counter reset every January. The 2025 policy change made it a one-time lifetime exemption, counting revenue earned from January 1, 2025 onward. For an app doing $30K MRR, that is the difference between never paying a share and paying 15% on most revenue from year three onward. Model it.
Big developers are excluded. Per the same Shopify documentation, developers earning $20 million or more annually through the App Store, or with $100 million or more in gross company revenue, pay 15% from the first dollar.
For an indie developer, the practical read is generous: your first million arrives essentially whole, minus payment processing and your costs. Very few platforms offer that. The catch is everything else in this article.
Distribution Is a Power Law
Nobody outside Shopify has complete revenue data, but independent analyses of listing and review data point the same direction. Week One Labs' 2026 benchmark analysis estimates the median listed app earns under $1,000 a month, with apps in the top tenth of their category plausibly in the $5K to $50K MRR range and the top 1% past $100K. GapQuery's writeup lands in similar territory. Treat all of these as educated estimates from public signals, not audited figures, but the shape is consistent with every app marketplace ever studied: a long tail of near-zero, a viable middle, a tiny head that earns most of the money.
Three implications follow from the shape:
- "Average" numbers will mislead you. The average is dragged up by outliers you will probably not be. Plan against the median and the middle band, and let the upside surprise you.
- Category choice is a revenue decision. The power law operates within categories too. A top-five position in a focused subcategory often out-earns a page-two position in a giant one.
- Survival is underrated. A large share of sub-$1K apps are abandoned within a year. Simply continuing to ship, support, and market past month twelve moves you up the distribution, because so many competitors remove themselves.
What Solo Developers Actually Report
The most honest data source we have is developers who publish their numbers, and the build-in-public corner of the Shopify ecosystem is unusually open. Reading across those public accounts, a few patterns repeat. Treat the figures as anecdote-derived estimates, because that is what they are.
The arc is slow, then compounding. The typical documented path spends three to six months under $500 MRR while reviews and ranking accumulate, reaches $1K to $3K MRR somewhere in the first year, and grows more steadily after organic discovery engages. Developers repeatedly describe the moment the App Store "starts working" as coming well after they nearly quit.
The full-time middle is real. The $2K to $20K MRR band is where documented solo and two-person apps concentrate, and at the upper half of that band the developer usually reports it as a comfortable full-time living. A handful of widely followed developers have documented runs to $50K MRR and beyond on the strength of one app plus sequels.
Portfolios are common. Many full-time indie developers run two to four small apps rather than one big one, both to diversify platform risk and because the second app launches into an audience and review base the first one earned.
Read public numbers with some skepticism, though. Build-in-public reporting has heavy survivorship bias: developers post milestones, not shutdowns, and the hundreds who quit at $200 MRR rarely write the retrospective. MRR screenshots also tend to appear at peaks, and MRR is not profit; a $10K MRR app with an agency retainer, a support contractor, and ad spend can net less than a quieter $4K app run solo. Use public accounts to calibrate the shape of the journey, not to set your own expectations to the loudest example in your feed.
The build side of this equation got dramatically cheaper: AI coding tools can scaffold a working app in days, as we covered in our look at building Shopify apps with AI tools. But that lowered everyone's cost simultaneously, so the store got more crowded and distribution became the differentiator. The revenue power law is really a distribution power law, a point we made bluntly in our Built for Shopify analysis.
The Cost Side Nobody Budgets
Gross revenue stories omit the ledger's other column. Here is an illustrative monthly P&L for a solo app at $5,000 MRR, with every line hedged as typical-range rather than universal:
| Line item | Illustrative monthly cost | Notes |
|---|---|---|
| Hosting and infrastructure | $50–$300 | Modest until real scale; spikes if you process heavy data |
| Tooling (analytics, errors, email, billing metrics) | $100–$400 | Subject to churn; see below |
| Payment processing | ~3% of revenue | On top of any Shopify share |
| Shopify revenue share | $0 | Until $1M lifetime; 15% after |
| Paid acquisition (if any) | $0–$1,000 | Optional, but organic-only growth is slower |
| Support time | 20–60 hours | The real cost, usually unpriced founder time |
| Rough cash costs | $300–$2,000 | Before valuing your own hours |
Two lines deserve expansion.
Support is the business. Merchants expect fast, competent help; reviews are the enforcement mechanism, and reviews drive ranking. Support hours scale with installs, including free ones, which is precisely why freemium apps can drown. At a few thousand installs, support is a part-time job you did not apply for.
Tooling churn is a real tax. The indie app stack depends on other small companies, and they have their own power-law problems. When Mantle announced it was shutting down, a large slice of the ecosystem lost its billing-and-metrics layer at once and paid a migration cost in engineering weeks. Budget occasional forced migrations as a cost of doing business, and prefer boring, replaceable tools where you can.
Add the recurring platform obligations: Shopify ships API releases on a quarterly cadence and retires old versions on a schedule, so an app is never finished, only maintained. If you are earlier in the journey, our Shopify app development guide covers what that maintenance surface looks like before you commit to it.
Two Paths: Niche Utility or Platform Play
Watching which apps make money reveals two workable strategies with almost nothing in common.
The niche utility. A focused tool for a specific merchant problem: bulk-edit something, sync something, display something. Small addressable market, weak competition, minimal support surface, high margin. Ceiling is real (often $5K to $30K MRR), but so is the floor, and one person can run it in ten hours a week once mature. This is the indie path, and stacking two or three of these is a genuine living.
The platform play. A big-category product (email, reviews, subscriptions, analytics) that competes with funded teams. The ceiling is seven or eight figures of ARR; the entry price is a team, a support organization, real marketing budget, and years. The middle of a big category is the worst place in the store: platform-play costs at niche-utility revenue.
The common failure is drifting between them: a solo developer in a giant category, out-resourced on every front, or a funded team on a niche too small to feed it. Pick a lane deliberately. Note that the niche path depends heavily on App Store organic discovery, which is why the ranking inputs (reviews, velocity, Built for Shopify) show up in every serious revenue story.
Both paths share one platform risk worth naming: Shopify absorbing your feature into core. It has happened repeatedly, from native subscriptions to built-in bundles, and each time a band of apps lost their reason to exist overnight. You cannot eliminate the risk, but you can price it in. Utilities that stitch together workflows across surfaces, or that serve a niche too small for Shopify to prioritize, tend to survive; single-feature apps sitting squarely on an obvious platform roadmap item tend not to. When Shopify's Editions announcements come out each season, read them as a competitor's product launch, because twice a year, for someone, they are.
The Acquisition Market
Shopify apps sell, and the buyer pool is deeper than most developers assume: individual acquirers, app portfolio companies that buy and operate dozens of apps, and occasionally strategic buyers rolling up a category. Market commentary such as Taylor Sicard's 2026 M&A overview sketches the current buyer mix.
On price, be skeptical of anyone quoting a precise multiple. Rough ranges observed in this market: healthy apps with stable retention and diversified acquisition have commonly traded around three to five times annual revenue, smaller or riskier apps below that, and strategic deals above it. Buyers discount hard for the risks this article has been describing: one traffic source, founder-only support, thin reviews, dependence on a single API surface that Shopify could absorb into the platform.
The useful reframe: everything that raises a sale price (retention, diversified installs, documented operations, support that runs without you) also raises the income of an app you keep. Build sellable; decide later.
If a sale within two years is plausible, start acting sold now. Keep clean monthly records of MRR, churn, and support volume from day one; write down operational knowledge instead of carrying it in your head; and keep business accounts untangled from personal ones. Buyers pay for what transfers, and every founder-only process is a discount you are voluntarily offering at the negotiating table.
A Realistic 12-Month Plan
Here is what a sober first year looks like for a solo developer starting from zero, with targets framed as working goals rather than promises:
- Months 1–2: Build narrow, validate live. Ship a focused utility against a problem you have verified merchants pay to solve. Test it against a development store, and ideally run a real Shopify store yourself for a month; nothing teaches merchant empathy faster than being one.
- Months 3–4: Launch and grind manually. Listing fundamentals, 20 personal merchant conversations a week, first 25 installs, first 10 reviews. Expect under $500 MRR and treat that as on-schedule, not failure.
- Months 5–8: Feed the flywheel. Review velocity, content for merchant problems, two agency partnerships, Built for Shopify requirements underway. Target: $1K–$3K MRR and organic installs exceeding manual ones by month eight.
- Months 9–12: Compound or correct. If retention holds, push the working channels harder and consider a small paid budget. If merchants churn fast, stop marketing and fix the product; marketing a leaky app is renting revenue. Target: $3K–$6K MRR and a decision, made with data, about whether this app is the business or the training run.
Twelve months to a part-time income that compounds is the honest median outcome for a good app marketed consistently. Faster happens; counting on faster is how apps get abandoned in month eight.
Run Your Own Numbers Before You Build
Before writing code, spend an evening on a one-page model: category, the top five incumbents' review counts, your price point, a conservative install curve, support hours per hundred installs, and the month your MRR crosses your minimum viable income. If the model only works with top-decile assumptions, change the category or the price, not the spreadsheet formatting. The model costs you an evening; the app will cost you a year. The developers who make real money on this platform mostly did not get lucky; they picked fights the math said they could win.