# After an iOS MVP gets traction, should I build native Android or a PWA?

URL: https://wonderful.so/blog/native-android-or-pwa-after-ios-traction
Markdown URL: https://wonderful.so/blog/native-android-or-pwa-after-ios-traction.md
Content type: Question and answer
Published: 2026-07-08
Updated: 2026-07-08
Author: Rulian at Wonderful
Asked by: An app founder
Tags: Mobile, Strategy, Product

## Question

After an iOS MVP gets traction, should I build native Android or a PWA?

## Answer

This is a business question wearing a technical costume.

Developers will turn it into native Android vs PWA, Kotlin vs web, App Store vs browser. Those details matter, but they're not the first thing I would look at. The first thing I would ask is a lot simpler: where are your users?

## I Wish PWAs Had Won More

I like PWAs in theory, and I think they should have taken off harder. One app-like experience, easier distribution, fewer store headaches, faster iteration. On paper, that sounds great.

But markets don't care what sounds great on paper. People expect apps and websites, and in some categories a PWA feels normal while in others it feels like you cheaped out, even if the technology is perfectly reasonable. That perception matters.

## Follow The Market

If your iOS MVP gets traction, don't immediately rebuild everything for Android just because a few people asked. Who is asking? Are they your actual market or just loud? Are they willing to pay? If you're going after Latin America, Asia, or other Android-heavy markets, Android may not be optional for long.

If you need broader access quickly and the product doesn't need deep native behavior, a PWA might be the right bridge. The mistake is treating platform as engineering trivia.

Platform is distribution.