The Problem
Stattus4 had 3 separate field apps — Collector for GPS-based data collection, Leak Inspection, and IoT Management. Each was a separate install, separate auth, separate updates. Field crews carried 3 icons. HQ shipped 3 release pipelines.
Consolidating into one app meant solving 3 problems at once. Shared auth and credential storage that survived offline use. Multi-language support for crews working in different regions. A navigation pattern that kept 3 apps' worth of features discoverable without becoming a menu maze.
The Approach
Embedded team building the super-app shell from foundation. Drawer-based navigation switches contexts without losing state. Centralized theming, secure credential storage (expo-secure-store), and i18next-driven internationalization across every user-facing string. CI/CD pipeline via GitHub Actions deploying to EAS for both stores.
Expo SDK 53 with React Native 0.79 and NativeWind. expo-maps + expo-location for the Collector's GPS-driven flows. expo-battery for device health monitoring on long field shifts. Sentry tracks errors per sub-app so issues surface to the right team. 12 documentation files covering architecture, deployment, testing, and contribution patterns set the foundation for scale.
Start a similar project.
Talk to us