Mobile AppCross-platformWebRTCNotifications

Cross-Platform Mobile Service Relaunch

We shipped one React Native codebase and stabilized call quality on carrier networks by moving to TURN relay infrastructure.

200K+
Active Users

Adoption grew after relaunch on iOS and Android from one shared codebase.

4.8★
App Rating

Ratings improved once call stability and booking flows were fixed.

40%
No-Show Reduction

In-app reminders and easier rescheduling reduced missed sessions.

On schedule
Major Rollout

The product met a fixed launch window tied to a commercial rollout.

Project Details

Industry
Mobile Services
Timeline
10 weeks
Role
3 engineers, 1 designer, 1 QA engineer
Technology Stack
React NativeNode.jsWebRTCAWSPostgreSQL

Problem

The client had an iOS-only app, no Android release, and unstable calls on mobile data. They had a fixed launch deadline and the product was not production-ready.

Approach

We built a unified React Native codebase, replaced their custom WebRTC setup with a configured TURN relay service, and tightened release QA for lower-end Android devices. The trade-off was higher relay infrastructure cost, but call reliability on real networks improved enough for launch.

Result

The team launched both platforms on time, increased adoption, and reduced missed sessions.

What Could Be Better

Push notifications on older Android devices were unreliable for the first six weeks. We fixed this in v1.2 with vendor-specific delivery handling.

Planning a similar rebuild?

Share your constraints and timeline, and we will map the technical path with trade-offs.