Why a $9.99 app shouldn't cost ₹830 in India: PPP pricing explained

Pure currency conversion is regressive — it charges users in low-PPP markets a much higher fraction of their income for the same product. Purchasing-power-parity pricing fixes it, and it almost always increases total revenue.

An iOS developer in San Francisco charging $9.99/month for a productivity app is, in a sense, doing the right thing — that's market rate in the United States. But when that same $9.99 price flows through to the Indian App Store, it lands at roughly ₹830/month. To a software engineer in Bangalore, that is the equivalent of an American paying somewhere around $40-$60/month for a productivity app — well above what most users in any market will reflexively pay.

The result is that the developer captures vanishingly few Indian users, attributes it to "the Indian market doesn't pay," and moves on. But the data — and the well-documented success of price-localized apps — tells a different story. The market doesn't reject paying; it rejects American prices.

This is what purchasing-power-parity (PPP) pricing fixes. Done right, it can lift global App Store revenue 15-40% without changing anything about your product.

What PPP actually means

Purchasing Power Parity is an economic concept used by the IMF, World Bank, and OECD to compare what a unit of currency can actually buy in different countries. The Big Mac Index, published by The Economist, is the most famous popular illustration: it tracks the price of a Big Mac in different cities and uses the variation to estimate over- or under-valuation of currencies.

Applied to App Store pricing, PPP gives you a fair-value baseline:

A price tier that takes the same fraction of local purchasing power as $9.99 takes from an American. — What "PPP-adjusted price" means, in plain English

Roughly, the World Bank's PPP conversion factor for India is about 22-23 INR per international dollar (vs. the market exchange rate around 83 INR/USD). The difference is exactly the gap that pure currency-converted pricing fails to close. A truly PPP-adjusted version of $9.99 in India is closer to ₹230-₹280 than ₹830.

The data on PPP pricing for digital products

Subscription-management vendor RevenueCat has published widely-cited research on local-pricing experiments across thousands of apps in their network. Their findings consistently support what you'd expect from price-elasticity theory:

• In low-PPP markets, lowering the local price typically increases conversion by more than enough to offset the lower per-unit revenue
• Total revenue from those markets grows even as the per-customer ARPU falls
• The effect is strongest in countries where the original USD-converted price was above what RevenueCat calls the "psychological threshold" — the price beyond which conversion drops sharply

The intuition: at $9.99 / ₹830 in India, you are not in the "expensive but worth it" range — you are in the "obviously not for me" range. Most users don't even attempt the trial. At ₹250-₹300, the same product becomes a normal-priced productivity app, and conversion jumps. The lost revenue per user is more than recovered by the higher fraction of users who convert at all.

"Raising prices in high-income countries and lowering them in low-income countries — done at the same time — almost always increases total revenue." — RevenueCat, summarizing findings from their local-pricing studies

What "right" looks like, by tier

You don't have to set 175 individual prices. The pragmatic approach is to group App Store territories into 3-4 tiers based on PPP, then map each tier to one of Apple's price points (Apple's price-tier system uses fixed price points per currency).

The exact breakpoints depend on your category — productivity apps and creative tools tolerate slightly higher prices in emerging markets than entertainment apps do. But this rough four-tier structure captures most of the value of PPP pricing without overengineering.

Won't I lose money from the high-PPP tiers?

This is the most common objection, and the answer is no — for two reasons.

1. Most of your revenue comes from premium tiers anyway. US, UK, Germany, Japan, Australia typically account for 60-80% of an indie iOS app's revenue. PPP pricing leaves those at full price. The change is at the bottom of the funnel where you're getting close to zero anyway.

2. The unit economics of low-PPP markets only get better with PPP pricing. A 60% increase in conversion in India at a 70% lower price still moves total Indian revenue up — typically significantly up, because most apps were converting near zero in those markets to begin with. You're going from "almost no revenue from India" to "real, growing revenue from India." That's a strict win.

What about App Store Connect's "Custom Pricing" feature?

Apple does support setting custom prices per territory in App Store Connect. The catch is operational: doing it manually means choosing a price point for each of 175 territories, every time you change your USD price. This is the entire reason most developers don't bother — the cognitive and time cost of manually mapping 175 territories to fair prices, then re-doing it whenever you raise or lower the base price, is enormous.

This is what tools like ours, plus Storely and a few open-source scripts, automate. You set a US base price; the tool maps PPP-adjusted price points across all territories using Apple's actual price-tier system; you push everything via the App Store Connect API in one click.

How to actually roll this out

1. Don't change all 175 markets in one go. Start with 8-12 high-impact emerging-market territories: India, Indonesia, Brazil, Turkey, Vietnam, Egypt, Mexico, Argentina, Pakistan, Nigeria, Philippines, Thailand.
2. Use the App Store Connect API to apply changes. Manual changes through the web UI are error-prone and don't scale.
3. Set a "future date" for the change in App Store Connect (subscriptions support this) so existing subscribers grandfather to old pricing — Apple's renewal-grandfathering rules are favorable to you here.
4. Watch conversion and revenue per market for 30 days. Apple's analytics in App Store Connect → Sales and Trends gives you per-territory revenue. You're looking for the local revenue line to rise, even though local price fell.
5. Iterate. Some territories may benefit from a slightly higher or lower tier than your initial mapping suggested. PPP gives you the right starting point, not the final answer.

The ethical case (which is also the business case)

It is worth being clear about something: PPP-adjusted pricing is also more fair. A monthly software subscription that costs an American 0.05% of their median income shouldn't cost a Bangladeshi 5% of theirs. Charging the same nominal USD price across the globe is a regressive pricing model — the people with the least pay the highest fraction of their income.

The business case and the ethical case point in the same direction, which is rare. Lowering prices in low-PPP markets makes your product accessible to more users and increases your revenue.

Tools and references

• World Bank — PPP conversion factors (the canonical data source)
• The Economist — Big Mac Index (intuitive PPP visualization)
• RevenueCat — local pricing research and case studies
• Apple — Custom App Pricing in App Store Connect
• appsops.store — automated PPP pricing across 175+ App Store territories