Bhava on Android: notes from a founder on shipping for both.

The Bhava Android beta is open today.

For a product that launched on iOS first, this is the expected second-shoe-drop. But for an Indian matrimonial product, Android first is the question — most of the Indian internet runs on Android. The reason we shipped iOS first is straightforward, and the reason we shipped Android next is also straightforward, and this essay is about both.

Why iOS first

The first hundred Members of Bhava — the cohort the Founder Concierge tier is built around — are heavily concentrated in the 1.5- and second-generation diaspora in the US, UK, Canada, Singapore, Australia, and the UAE. In every one of these markets, iOS share for the 28-to-35 educated diaspora segment is between 65% and 85%. The same cohort's parents — who are the family curators — own iPhones at roughly the same rates.

The decision to ship iOS first was the decision to ship the platform the diaspora cohort uses. India-resident urban Members, who lean Android, were going to be the second-wave audience; the matchmaking efficiency between iOS-first-wave and the eventual Android-second-wave was going to be high regardless, because cross-platform matching is the entire point of the matchmaking engine.

Shipping iOS first also let the first version go through one App Store Review process at a time, ship one set of capabilities, and reach the first cohort with a single coherent product surface. The cost was the four-week-or-so delay before Android-resident Members could join. That cost was acceptable.

Why Android second

The Bhava product without Android is incomplete. Two reasons:

One, the urban Indian Member share is a meaningful slice of the matrimonial pool. A Bay Area diaspora Member is statistically more likely to match with a Mumbai or Bangalore Member than with a fellow Bay Area Member, by the simple math of where most Indians live. The pool of compatible candidates is dominated by India-resident Members. An iOS-only Bhava leaves most of that pool out of reach.

Two, the family curator role inherits the same Android prevalence. A Member's parents in Pune, regardless of the Member's own iOS preference, are statistically likely to be on Android. The family-curator account on Android needs to be at parity with iOS for the Family-Active architecture to actually work as designed.

The Android beta opens today to address both.

What the Android beta is

The Android beta is functionally complete with iOS feature parity, with the following caveats:

StoreKit / Google Play billing differences. Premium subscriptions on Android are billed via Google Play, not Apple. The pricing is the same; the billing path is different. Subscriptions purchased on one platform do not currently transfer to the other (a roadmap item).

Push notifications via FCM on both, but with platform-specific delivery behavior. Lock-screen notification design differs between iOS and Android by OS convention. The notification content is identical; the rendering is platform-native.

Sign-in providers. Apple Sign-In is the primary auth on iOS. Google Sign-In is the primary auth on Android. Both apps support both providers, so a Member who signed in via Apple on iOS can sign in via Apple on Android (and vice versa for Google).

No widget on Android v1. The iOS app has a home-screen widget showing the daily introduction. The Android v1 does not — Android widgets are higher-effort and we deferred. Roadmap item for the public release.

Google Play Store review timing. As of writing, the Android build is in Google Play's internal testing track, not public. Members can join via the beta invite link. The public Play Store listing follows in roughly two weeks pending Google's review.

What Android changes structurally

Adding the Android cohort changes the matrimonial pool in three ways worth flagging.

The pool roughly triples in the next 90 days. Most current waitlist signups from India-resident candidates have been waiting for Android. As they convert, the diaspora cohort sees a meaningfully larger and more diverse set of candidates each Sunday morning. The Founder Concierge curation gets richer to draw from.

The family-curator share on Android will outpace iOS over time. Diaspora Members' parents — who in many cases live in India — are the largest segment of family curators. The Android app is what brings them into the Family Hub in serious numbers.

The cross-geography matching becomes the default. The first 100 Members on iOS have been matching primarily within the diaspora. With Android, cross-geography pairings — Mumbai-to-Brooklyn, Pune-to-Toronto, Delhi-to-London — become the statistical norm. This is what the matrimonial product was always intended to support.

What it means for the Founder Concierge tier

The Founder Concierge cohort cap is still 100 Members. Android signups join the same cohort. Sunday-morning curation continues at the same cadence with the same single-introduction-per-Member rule. The richer candidate pool means the per-Member curation depth improves — there are more candidates to consider when I sit down each Sunday — but the time budget per Member does not increase.

The 12-to-16-week Concierge tier timeline remains. Cohort fills first; algorithm matures during that window; algorithmic Bhava goes live for new Members joining after the cohort closes.

How to join the Android beta

If you are an existing iOS Member: nothing to do. You can install the Android app on a second device using the same sign-in if you want, but your matrimonial profile is platform-independent.

If you are new to Bhava on Android: the beta invite link is on the Bhava website. Tap the Android download CTA. You will land in Google Play's internal testing track via the invite; install proceeds normally from there.

If you are a family curator joining on Android: install via the same link. The Family Hub onboarding is identical to iOS.

---

A closing personal note. Shipping the Android app today is, for me, less a feature milestone than a structural one. The Bhava thesis is that the Indian matrimonial market wants a Vedic-tradition matrimonial product expressed in 2026-native software. 2026-native includes Android — natively, not as an afterthought. We are now there.

— Himanshu Batra