Why iOS first when Splitwise scaled on Android

Quick answer: Wendir launches iOS-first despite Splitwise's Android dominance because (1) a small team ships higher quality on one platform than two, and quality compounds; (2) our launch demographic (group-trip organisers, 25-45, professional, in AU/US/UK/NZ/SG) skews iPhone 55-70%; (3) the interactions we lean on (receipt scanning, Apple Pay, Live Activities, iOS share sheet) are higher-fidelity on iOS in 2026. The accepted cost: 30-45% of target users lost for the first 12-18 months. Android comes in late 2027.

Splitwise has tens of millions of users (most-cited public figure was roughly 50 million as of 2023). The majority of them are on Android.

So is Uber's user base. So is WhatsApp's. So is most of the consumer software that scales globally — Android is roughly 70% of the world's smartphones, and outside North America and a few other markets, it's the default.

We're launching Wendir on iOS first anyway.

This piece is the short version of why, what it costs us, and why we still think it's the right call. If you disagree, fair — we'd be making a different call at a different stage.

The honest reasoning

It's not ideology. It's three pragmatic trade-offs.

1. Quality compounds; spread doesn't

A small team shipping two mediocre platforms produces less total value than a small team shipping one excellent platform. Quality compounds — a polished, fast, opinionated v1 builds the trust that earns the second cohort. Two half-baked v1s build trust on neither platform.

This is a universal lesson but it's especially true for a product whose differentiator (specialised agents, citations, the interaction loop) is sensitive to polish. If the agents feel laggy or the receipt-scanning workflow is janky, the whole product feels worse — not just the broken part.

So: pick one platform; make it excellent. Spread later.

2. Our target user disproportionately uses iPhone

The closed-beta audience we're targeting: Australia, US, UK, NZ, Singapore. The demographic: 25-45, urban, professional, organises group trips, has the budget for A$49/year. In these markets, that demographic skews iPhone by a wider margin than the country average. Best-available data puts iPhone share among this segment at 55-70% in the launch markets, vs roughly 25% globally.

Targeting general smartphone share would be the wrong number. Targeting the share of the people who would actually use Wendir is the right number, and that number favours iPhone.

This is the same logic Splitwise didn't follow in 2011, but Splitwise was launching into a different demographic (cost-conscious students splitting rent and groceries) and a different platform landscape (iPhone was a luxury good outside the US). The right answer for them isn't the right answer for us.

3. The interactions we care about are higher-fidelity on iOS

The features Wendir leans on:

• Receipt-scanning via camera. Vision APIs on iOS are mature and predictable. Android has the same APIs in theory; in practice the device fragmentation creates a long tail of edge cases.
• Apple Pay / PayID instant settlement. iOS-native, no friction. Android has Google Pay but the user experience is more variable.
• Location updates during the trip. Background location on iOS is more battery-aware than across the Android device matrix.
• iOS share sheet for sending links into Scout. Universal extension surface, predictable behaviour.
• Live Activities / Dynamic Island for trip-state. Genuinely useful for "your day is starting; first stop in 45 minutes" — and a feature that has no Android equivalent.

Could we build the same product on Android? Yes. Would the first cohort's experience be as polished? No. The decision is about where the first 12 months of polish goes, not which platform is intrinsically better.

What the decision costs us

Real costs, named honestly:

• We lose 30-45% of our target users for the first 12-18 months. The range follows from iPhone's 55-70% share in our launch markets — see below. Some will sign up to the waitlist and quietly churn before we get to Android; some won't even try.
• Network effects suffer. Group trip planning is multi-user by definition. If three friends are on iPhone and one is on Android, the whole group can't use Wendir until the Android friend can. We lose the trips where any group member is on Android.
• The press narrative is harder. "iOS-only" sounds boutique and elitist; the reviewer will compare us unfavourably to apps that launched on both. We accept this; we won't pretend the trade-off doesn't exist.
• Geographic markets are constrained. Latin America, much of Asia, much of Africa are predominantly Android. We can't credibly expand into those markets without Android, which means we're geographically narrower than we'd like for the first 18 months.

These aren't theoretical. They are the real cost. We've decided they're worth paying for the quality compounding from focus.

Why not cross-platform (React Native / Flutter)?

The standard alternative — write once, run twice — is tempting. We've considered it and rejected it for Wendir specifically.

Cross-platform frameworks save time on the build. They cost time on:

• Performance. A 60fps native UI with platform-correct gestures is meaningfully different from a 50fps cross-platform one. Users feel the difference even when they can't name it.
• Accessibility. VoiceOver and TalkBack work better with native components.
• Platform integration. Apple Pay, Live Activities, iOS share sheet, Google Pay, Android share intent — every one of these is a custom bridge in a cross-platform app.
• Maintenance. Two platforms' worth of edge cases through a single codebase produces a long tail of "works on iOS, not on Android" bugs.

For an app whose differentiator is polish and platform-native interaction, the cross-platform compromise costs more than the build savings. We'll write Android natively in Kotlin/Compose when we get there. Two codebases, both first-class.

What it doesn't mean

A few clarifications:

• It doesn't mean we think iOS users are more important. It means iOS is where the polished first version will land. The second cohort matters as much as the first.
• It doesn't mean we'll never ship Android. Android is on the roadmap, not the discard pile. The wait is finite.
• It doesn't mean cross-platform is bad. It's the right answer for many products. For Wendir specifically, the trade-offs don't favour it.

The shortest version

Three things:

1. Quality compounds; spread doesn't. A small team that does one platform excellently builds more trust than the same team doing two platforms poorly.
2. In our target markets (AU/US/UK/NZ/SG) and demographic (group-trip-organisers, 25-45, professional), iPhone share is 55-70%. That's the right denominator, not global smartphone share.
3. iOS-first costs us 30-45% of our target users for the first 12-18 months. We've accepted that trade-off. Android comes when iOS clears its quality bar — late 2027, realistically.

Where this fits

This is the second piece in the Founder Dispatches lane. The series so far:

• Why we're building Wendir — the trip that broke us.
• This piece — the launch strategy.

If you want to argue the call, the comments aren't open — we're not running comments — but the waitlist signup has an optional "what would you tell us" field. We read all of them.

---

Written by the Wendir team. Last updated: 15 May 2026.