How Softweb migrated United Through Reading’s mobile app from Xamarin to React Native with zero downtime
Our client, United through reading (UTR), is a nonprofit that supports military families through shared story-time experiences, with a presence across 200+ recording locations worldwide.
They partnered with Softweb to migrate their Xamarin-based mobile app to React Native, preserving core features while maintaining uninterrupted access for over 3.3 million military family members.
Industry: Nonprofit 
Business type: Digital nonprofit platform - Services: Mobile application modernization
- Technology: React Native, AWS, Firebase, .NET
Client profile
UTR is a nonprofit focused on helping military families stay connected during deployments. Through a secure mobile app and a network of over 200 recording locations, service members can record and share story-time videos with their children from anywhere in the world.
The organization’s platform has reached more than 3.3 million military family members, supporting emotional well-being and literacy development for children whose parents are serving away from home.
Technical challenges
UTR’s mobile app was built on Xamarin, which supported cross-platform recording and content delivery across iOS and Android. As the framework approached end of support, the underlying stack could no longer provide the reliability, security coverage, and update continuity required for continued use.
Framework end-of-life
Xamarin reached end of support, bringing security and compliance concerns into focus. Security patches were no longer consistent. Over time, exposure to known vulnerabilities increased. Newer platform requirements also became harder to keep up with as updates became less reliable.
Feature consistency risk
Offline recording, secure storage, and the in-app library needed to be preserved during the migration so users could continue using them without disruption. Any change in their behavior could interrupt usage, particularly when connectivity is limited.
Maintaining uninterrupted access
The application supports recording and sharing stories, along with access to videos that help families stay connected. Access had to remain available throughout the migration. Even short downtime could delay uploads or interrupt that connection between users.
Uncertain migration path
Tooling gaps, limited plugin support, and build stability concerns across platforms made the direction less straightforward. Differences in ecosystem maturity also made comparisons harder. Some options appeared viable at first but raised concerns when evaluated for long-term use.
Our solution
We ran a proof-of-concept that helped us compare .NET MAUI and React Native under similar conditions. React Native delivered more consistent results during testing, making it a more reliable option for the migration.
The migration followed a phased rollout to keep the application accessible throughout. Each stage included regression checks, crash monitoring, and performance validation, allowing updates to roll out while the application remained in use.
Code audit and logic separation for a cleaner migration
We reviewed the existing Xamarin codebase to understand how business logic and UI components were structured. In areas where these layers were tightly coupled, they were separated to allow core functionality to remain intact while the interface was rebuilt independently.
Separating these layers reduced rewrites and allowed existing logic to be reused during migration. A more modular structure also made future updates easier to manage and reduced effort in maintaining the codebase.
Component re-engineering with consistent user experience
The interface was redesigned using React Native components, with existing layouts, navigation paths, and interaction patterns carried forward as they were. The focus stayed on familiarity, so users could continue using the application without having to adjust to a different experience.
Platform-specific differences were handled through small, targeted adjustments wherever required. A shared logic layer was maintained to keep application behavior consistent across iOS and Android and simplify future updates.
Native bridges connecting video capture and cloud services
Existing Swift and Kotlin modules used for video capture were integrated into the React Native architecture using native bridges. The integration preserved the recording experience without requiring changes to performance-critical components.
Backend integrations, including AWS storage, media processing, and notification pipelines, were retained as part of the existing setup. Retaining these integrations ensured continuity while enabling the flexibility of a cross-platform architecture.
Offline-first recording with automatic upload on reconnection
Offline recording was carried forward during migration, as it plays a critical role in low-connectivity usage. The existing feature was preserved as part of the transition, allowing users to record videos locally, with files remaining on the device until a stable connection is available for upload.
The interaction remains unchanged from a user standpoint. Recording and upload continue to work reliably across varying network conditions.
Regression testing and performance monitoring across migration phases
Automated regression testing was introduced at each stage of the migration to confirm that existing features continued to function as expected. Crash monitoring and performance checks were added to identify issues early.
A structured validation process allowed the migration to progress steadily across phases. By the final release, the application had been tested across key scenarios, supporting a smooth transition without disruption.
Business goals and measurable outcomes
| Business objective | Business benefit delivered |
|---|---|
| Modernize the mobile platform | Migration to React Native established a stable and actively supported foundation for ongoing development and platform updates |
| Enable faster feature delivery | A simplified and modular code structure reduced dependencies, enabling quicker development cycles and faster feature releases |
| Reduce development overhead | Maintaining a single shared codebase across iOS and Android minimized duplication and lowered ongoing maintenance effort |
| Reduce long-term security risk | The modern, supported framework ensured ongoing security coverage and alignment with evolving platform standards |
Tech stack
- Frontend (Mobile Apps):
- React Native (iOS & Android), JavaScript, Native Modules (Swift, Kotlin)
- Database:
- Amazon RDS (PostgreSQL), SQLite (Offline Storage)
- Cloud & Infrastructure:
- Amazon Web Services (AWS), Amazon EC2, AWS ECS
- Media & Storage:
- Amazon S3, AWS Elemental MediaConvert
- Notifications & Messaging:
- AWS SNS
- Security & Identity:
- AWS Identity and Access Management (IAM)
- DevOps & Tools:
- GitHub, Visual Studio 2022, Visual Studio Code
- Platform Tools:
- Xcode (iOS Builds), Android Studio (Android Builds)
- Architecture:
- Cross-Platform Mobile Architecture, Offline-First Capability, API-Driven Design
Similar case studies
How Softweb built a fleet management and vehicle auction platform for Emkay
Connect Now
Our experts would be eager to hear you.
