If your budget is tight, choosing Android first is almost always the wrong move when you can only afford to build for one platform. I just watched this Waveform episode from MKBHD’s team, where they break down why so many apps launch on iOS first, and the developers they interviewed were brutally honest about it. Here’s the link: https://lnkd.in/efsbqFbx The reasoning wasn’t “iOS is better.” It was math. iOS captures roughly two-thirds of global app revenue, despite Android dominating unit share Subscription ARPU on iOS is multiple times higher than on Android. In the US and Canada, the paying segments skew heavily toward iPhone users. Supporting Android requires more devices, more QA, and more edge-case bugs. iOS adoption is unmatched — 76%+ on the latest OS within months If you're an indie dev or building on a limited budget, these numbers matter. They decide whether your v1 survives long enough to see v2. And to be clear, this isn’t coming from an anti-Android place. I like Android. I own an Android tablet. There are entire categories where Android is the better playground. But here’s the real point: 🟦 If you can only afford ONE platform: → Pick iOS. 🟩 If you can afford ONE codebase that reaches BOTH: → Pick React Native or Expo. React Native (or Expo) provides the optimal balance of reach, cost efficiency, and learning speed. Why? 1️⃣ You get a real signal from both ecosystems early Who signs up, who pays, and what devices they use. That matters more than perfect polish on day one. 2️⃣ You maximize reach per engineering dollar One team, one codebase. Even 70–80% shared code is a massive win. 3️⃣ You can still go native where it counts: Camera, BLE, animations Write modules natively and keep the rest unified. 4️⃣ You avoid locking your business into one demographic iOS monetizes better, but depending on your vertical, your actual power users might be on Android. So my rule with a limited budget: Could you validate the idea? Go cross-platform. Already validated, with substantial revenue and an iOS-heavy audience? Go native where it adds value. The Waveform episode explains why devs default to iOS-first. But that doesn’t mean you should repeat the pattern without thinking. If you’re budget-constrained, optimize for reach, learning speed, and iteration velocity. #SoftwareEngineering #MobileApps #ReactNative #ProductStrategy
Kyle Szives I agree 100%. I’ve had parallel iOS and Android apps serving the same market for over 10 years, and no matter what new stuff each platform adds, the ratio is always 2:1 in favor of iOS just in terms of user counts.
Smart breakdown. Building for where revenue actually converts is what keeps early products alive.
I would not start with a mobile app on a stringshoe budget, full stop. People use upward of 10 apps on their phone, iOS/Android it doesn't matter. Why would they use yours? Starting with a mobile friendly web app makes much more sense. The only reason to start with a mobile app (regardless of platform/code language choice/framework) is when mobile app is the ONLY thing that makes sense for the product. It's irrelevant if you don't have the budget for marketing, why would someone see your app? doesn't matter what platform. BTW, in most of the world Android dominates the market, especially since the phones are much cheaper than iPhones.
You know from my experience, iOS dominates in the US market, but Android dominates the rest of the world. If your target market is primarily US/Canada, iOS-first makes sense. But if you're targeting the rest of the world, you should think Android-first. For instance, all the clients I worked with abroad had Android as their main focus Geography matters more than general platform advice. Know where your users are before choosing. Would love to hear your thoughts on this Kyle ♥️