Back to Journal
Mobile AppsNº 007June 21, 20267 min

What it really costs to ship a native app on both stores in 2026

Store fees are the cheap part. The real cost hides in what no invoice shows you: maintenance, rejected reviews, and the second operating system.

Someone told you that launching an app costs 25 dollars. Technically, that's not wrong. It's what Google charges, once, to open a Play Console account.

But that number is a trap. It's like saying that opening a restaurant costs the price of the business license. The license is real. It doesn't pay for the kitchen, the staff, or the fridge that dies in August.

Let's get to what it really costs, in 2026, to put a native app on both stores and keep it alive.

Store fees are the smallest item on the list

Apple charges 99 dollars a year for the Apple Developer Program. Don't pay it, and the app goes dark. It's rent, not a purchase.

Google charges 25 dollars, a single time, to register the developer account on the Play Console. You pay once and you're done.

Add it up and the first year runs you about 124 dollars in official fees. Keep that number. It's the one cost everyone knows about, and the least important of them all.

It's two apps, not one

Here's the part that wrecks budgets. When you say "native app for both stores," you're asking for two products with two operating systems, two base languages, and two review teams with different rules.

iOS is Swift and Xcode. Android is Kotlin and Android Studio. Different tools, different build cycles, different bugs. What breaks on one side doesn't break on the other.

Frameworks like React Native or Flutter promise shared code. They help, and we use them. But they don't make the problem go away. You still need a Mac to compile for iOS, accounts on both sides, and real phones from both worlds to test on. The checkout screen that works on the Pixel fails on the iPhone with a notch. It always does.

The typical scenario goes like this: you budget for one app and get, in practice, one and a half. The second half shows up when the client opens the Android version and notices the keyboard covering the login field.

The cost that shows up on no invoice

There are expenses nobody mentions up front because they don't fit on a clean quote. These are the ones that separate a project that lives from one that dies three months in.

  • A rejected review. Apple enforces the App Store Review Guidelines with a heavy hand. One poorly justified permission, a missing delete-account button, and the app goes back. Each round is days of dead time.
  • A Mac. There's no iOS build without Apple hardware. If you don't have one, it's a purchase or a cloud CI service with a monthly bill.
  • Push notifications. You need Firebase on Android and APNs certificates on Apple. Each breaks in its own way and renews itself less often than you'd like.
  • Annual maintenance. Every new version of iOS and Android can break something. Don't update, and the app decays until it stops installing on new phones.
  • Privacy compliance. App Privacy on Apple, Data Safety on Google. You declare what you collect and you have to actually live up to it, under GDPR.

So, honest numbers

I'm not going to invent a figure billed by a company that doesn't exist. But I can give you the cost structure we see in real projects.

Official fees: about 124 dollars in the first year. Development: depends on scope, and this is where ninety percent of the money goes. Maintenance: count on a recurring fraction of the build cost, every year, indefinitely.

The mental rule I give clients is simple. A launch is a marriage, not a dinner. The entry cost is the easy part. The commitment is what weighs on you.

There's a cheaper path, and sometimes it's the right one

Not everything needs to be native. A Progressive Web App installs straight from the browser, runs on both systems with a single codebase, and dodges store fees and reviews. For plenty of businesses, that's more than enough.

What you lose is the badge of being in the store, some deep hardware access, and the trust an App Store icon still conveys. If your app sells trust or needs reliable push notifications on iOS, you'll want native.

The right question isn't "what does it cost to ship on both stores." It's "do I actually need both stores." Answer that first. It saves you more than any price negotiation.


If someone hands you an app quote with no line for maintenance, they're not hiding the cost. They're pushing it six months down the road, once you've already signed.

References
  1. 01Apple Developer Program
  2. 02App Store Review Guidelines
  3. 03Google Play Console — registration fee
  4. 04web.dev — Progressive Web Apps
  5. 05Google Play — Data safety
Also:
Performance & SEONº 006

What a 4-second LCP does to your checkout conversion rate

Four seconds sounds like nothing. At checkout, it's the gap between a closed sale and an abandoned cart.

Web for SMBsNº 005

Why your 2019 WordPress site is costing you customers in 2026

Seven years is an eternity on the web. The site that looked modern in 2019 now pushes customers away before the first contact. Here's why.

Back to Journal