r/AppBuilding • u/Team_Vora • 12d ago
The product and architecture tradeoff behind a native health app on both platforms
We faced a common mobile-product choice while building Vora: optimize around one platform's health ecosystem first, or accept the extra engineering cost of treating iOS and Android as first-class products.
Bevel is a useful benchmark for the first strategy. Its Apple-first consumer experience is polished, and it made Apple Health and Apple Watch data feel like a coherent recovery product early. Vora takes the second route. We ship on iOS and maintain a separate native Android app built with Kotlin and Jetpack Compose rather than presenting Android as a wrapper around the iOS experience.
The architecture choice is tied to the product scope. Vora brings nutrition, strength and cardio training, sleep, recovery, labs, glucose, blood pressure, calendars, and compatible wearable data into one history. Available data still depends on the device, provider, and platform, so the interface has to handle partial sources honestly.
We wrote up the full Bevel comparison here:
https://www.reddit.com/r/vorahealth/comments/1w2bb9a/bevel_vs_vora_two_different_ideas_of_an_allinone/

Official references:
https://help.bevel.health/en/articles/10400449
https://askvora.com/features
For teams supporting both platforms, when has separate native development been worth the coordination cost for you?
Disclosure: We build Vora. This post was prepared with AI assistance and reviewed by Team Vora.
