Start with three questions about this year
Before touching any price, pull your 2026 numbers and ask three questions. First, which tier actually sold best — the one that brought in the most paying users month after month, not the one you hoped would. A $9.99 tier quietly outselling your $4.99 tier says your users were never as price-sensitive as you assumed — the cheap tier may be anchoring the whole page down. Second, which tier lost the most subscribers. Look at churn per tier, not overall — heavy churn in one tier is usually a promise problem, not a price problem: the fastest leavers are the ones whose expectations the tier set wrong. Third, has your cost line moved. Server bills, support time, the store fee, the tools you pay for monthly — if serving a user got dearer through the year while the price stayed flat, your margin shrank without anyone deciding it should. Answer all three from your own dashboard, not a benchmark article. The app pricing calculator takes the same three inputs — payers, price, costs — and shows what your tiers actually earn, so the review starts from your numbers, not a hunch.
The 2027 pricing checklist
How many tiers do you really need? Most indie apps do fine with two or three. One tier forces every buyer into a single yes-or-no, and four or five tiers turn the pricing page into a comparison spreadsheet nobody finishes reading. Two paid tiers plus a free tier is a sensible default; add a third only when the middle one has a distinct job, like a team plan or a power-user feature the other two cannot offer.
Where does the free tier end? A free tier should end where the user feels the value — not before it, not long after. If free users never hit the limit, nothing converts; if they hit it on the first screen, they leave before they care. The honest test is your own usage data: find where your most engaged free users start bumping into the wall, and put the paywall there. The freemium app pricing guide works through that boundary in full, including what to give away and what to hold back.
Is your annual discount buying renewals, or giving money away? An annual plan is a trade: you give up roughly two months of revenue for cash up front and a subscriber who cannot churn for a year. It only pays if those buyers would otherwise have churned before month ten. Check it: of last January's monthly starters, how many were still paying in October? If most were, a 20% annual discount is mostly a gift; if half were gone by June, it is cheap insurance. Our subscription pricing guide covers the monthly-versus-annual arithmetic in detail.
Does your price still make sense outside the US? A $4.99 price is a different share of a day's pay in different markets, and the stores handle the conversion differently — Apple re-adjusts prices when currencies move, Google converts once on the day you set the price. Pick your three biggest non-US markets, look at what your price converts to there, and ask whether you would still buy it. If the answer is no in a market that already brings you users, a local price point is worth more than another tier.
Change one variable, then wait four to six weeks
The most common year-end mistake is changing everything at once — new tiers, a new annual discount, a higher entry price — and then having no idea which change did what. Pick one variable and leave the rest alone. Two good candidates: the annual discount, or the entry tier. Raise the annual discount from 15% to 25% and watch whether the share of new subscribers choosing annual moves; or raise the entry tier by $1 and watch conversion, not revenue — revenue can rise for a month while the buyer pipeline quietly thins. Run it for four to six weeks, long enough to cover a full monthly renewal cycle, and judge it on the metric you wrote down before you started. If that number moved the wrong way, revert — a test you can undo is a test; a change you are stuck defending is a mistake. A one-time purchase is the one case where testing is harder, with no renewal cycle to read — test the price on new users only, and give it the same four-to-six-week window.
A worked example: raising the price by $1
The numbers below are a worked example with stated assumptions, not benchmarks — your conversion rate will differ; the point is the method. Assume 10,000 monthly active users, 3% of whom pay (300 payers), a single $4.99 tier, and the store's 30% cut.
- Today, at $4.99. 300 payers × $4.99 = $1,497 gross per month, about $1,048 net after the 30% store cut. At the 15% small-developer rate the same month nets about $1,272 — check the rate before you model, because it moves the answer by more than the price rise below.
- Raise it to $5.99, conversion holds. 300 payers × $5.99 = $1,797 gross, about $1,258 net at 30% — roughly $210 more a month for changing one number. This is the case every price-rise pitch quietly assumes — real only if nobody leaves.
- Raise it to $5.99, conversion slips half a point. 2.5% of 10,000 is 250 payers × $5.99 = $1,497.50 gross, about $1,048 net at 30% — essentially the same money as today: the extra dollar per buyer is exactly cancelled by the fifty buyers who did not convert.
That is the trade in one line: a $1 rise is worth it only if conversion falls by less than half a point. Put your own numbers through the same sum in the app pricing calculator and find the break-even drop for your app before you touch the price. If the break-even drop is tiny, the rise is a gamble; if it is wide, the rise is cheap.
Before you change anything: your existing subscribers
Decide what happens to the people already paying before you save a new price — the two stores treat them differently, and the choice is hard to undo. On Google Play, existing subscribers are unaffected by default — they stay on their original price in a legacy price cohort — and moving them to a higher price is opt-in by default: each subscriber has to actively accept the new price, or Google Play cancels the subscription. On the App Store, you can preserve the current price for existing subscribers when you plan the change, so only new subscribers pay more; apply an increase to existing subscribers and a small one is notified rather than consented to, while a large or repeated one needs consent. For a first price rise, grandfathering is the low-risk default on both stores: new subscribers pay the new price from day one, nobody already paying gets a surprise, and you can revisit the grandfathered cohort later once the new price has proven it converts. New purchase prices typically take effect within hours on Google Play, and scheduled changes on the App Store need a start date a day or two out — set the date, then check the console rather than assuming it is live. The thresholds and notice periods above are the current public position as of late 2026 and the stores adjust them; confirm them in the console when you make the change, and treat the console as authoritative if anything here has moved on.
App pricing for 2027 FAQ
When is the best time to change my app's price?
Year-end is the practical window: you have a full year of sales data, users are already thinking in new-year plans, and a January change reads as a fresh start rather than a cash grab. The timing matters less than the method, though — change one variable, run it for four to six weeks, and compare against the same assumptions you started with, instead of changing the price, the free tier and the annual discount all at once.
Should I raise my app's price by $1 for 2027?
Only if the arithmetic survives a conversion drop. Under the stated assumptions in this guide — 10,000 monthly users, 3% conversion, a $4.99 tier — raising the price to $5.99 lifts monthly net revenue from about $1,048 to about $1,258 at the 30% store cut if conversion holds. If conversion falls half a point to 2.5%, net revenue lands back at about $1,048 — a wash. The $1 is worth it only if you have a reason to believe conversion will hold.
Do I have to raise the price for my existing subscribers too?
No — on both stores you can leave existing subscribers on the price they signed up for and charge new subscribers the new price. On Google Play, existing subscribers stay on their original price by default in a legacy price cohort, and moving them to a higher price is opt-in by default. On the App Store you can preserve the current price for existing subscribers when you plan the change; a small increase applied to existing subscribers is notified rather than consented to, while a large one needs consent. Store rules change, so confirm the current thresholds and notice periods in the store console before you schedule anything.
Run your own 2027 numbers
That is the method; the calculator is the arithmetic. Put your monthly users, conversion rate and price into the free app pricing calculator: it shows net revenue at $4.99, $9.99 and $19.99 after commission, plus the exact price to hit your target. Then run the $1-rise test on your own numbers — find your break-even conversion drop, and let that number, not the calendar, decide whether 2027 starts with a new price. The general how to price your app guide is the next place to look.