Turning an established EHR web workflow into a mobile-first product for internal beta
An established healthcare company needed a new React Native product that translated, rather than merely copied, its web application for therapists and practice staff.
This story comes from Chris Martinez’s prior professional experience and is not presented as a CAM Software client engagement.
The decision
Use existing business logic and APIs where they fit, while redesigning the experience around mobile authentication, lighter payloads, multi-account calendars, messaging, and mobile-first use.
Observed result
The internal beta created a controlled learning window in which product and QA could gather feedback and resolve issues before broader external use.
The decision, visualized
Internal beta → controlled learning
Internal beta access gave product and QA a controlled learning window before broader external use.
The situation
An older Xamarin application existed but was not the future. The company wanted React Native and needed the new product to reflect the mature web system while recognizing that a therapist on a phone has different constraints than a user at a desktop.
Product decisions
The mobile product emphasized faster session restoration and biometric login, multi-account calendar access for managers, messaging, and lightweight API usage. It was mobile first and tablet second, with responsive behavior and careful reuse where the web foundation made sense.
Delivery system
A structured AI-assisted engineering cycle helped with planning, implementation, review, and quality, but the result still depended on experienced human decisions about architecture, scope, product behavior, and release readiness.
Why the internal beta mattered
The beta window was not treated as spare capacity for unrelated scope. Product and QA used it to gather feedback, repair issues, and improve their understanding before a wider external beta. Finishing implementation only creates value when the release and learning system can use it.