Trailing React Native in a Legacy Mobile App
summary
Regal pulls React Native into a legacy ticketing app that does millions in revenue, shipping a brownfield, page-by-page strangler fig migration with feature flags and a goal of porting ~90% to JS. The stack uses Expo, Expo modules and a customized self-hosted OTA updater so updates hit users fast; local hot reload and a three-month trial prove iteration speed. CI code signing for XC frameworks causes pain, and UI automation uses Maestro + Claude for regression screenshots.
AI-written summary · about
chapters (12)
- 0:00React Native in legacy apps
- 1:12Regal Cinemas adoption
- 2:15Multi-platform UI challenges
- 3:40Expo and React Native choice
- 4:43Brownfield approach
- 5:47Strangler fig migration
- 6:53Stack and OTA updates
- 7:13Live React Native demo
- 7:55Local dev benefits
- 8:36Automated UI testing
- 9:39Lessons learned
- 10:22Demo project
related talks
35mMigration Web (Angular) to Mobile Development (React Native)
51mRapid App Development With React Native: Lessons Learned at NSB
10mGreenfield of Dreams
01h 13mMigrating to React Native: A long-term retrospective
17mDispatches from React Native
30mStrategies For Using React Native In A Brownfield App
50mReact Native hindsight from Pl@ntNet
07mFrom Native to React Native