One thing I learned migrating a mobile product from a WebView MVP to React Native: the hardest problems usually aren't the screens.
On Beepr, the real blockers were background execution, geolocation reliability, push notifications, slow geospatial queries, and backend logic that had grown without a clear audit trail.
I led the migration to React Native with Supabase, PostgreSQL, PostGIS, and native background capabilities. I also audited 51 Supabase Edge Functions and designed a zero-downtime cutover so the product could keep serving users during the transition.
The takeaway: before rebuilding a mobile app, find out which problems are architectural and which are merely visual. A prettier interface won't fix unreliable background services, weak location enforcement, or slow queries.
Curious what other teams have found when moving from a WebView-based MVP to a production mobile app.
8:58
1
2
306
