Migrate everything to React Native? #2
Description
The current implementation is web-based, which limits the app to browser/PWA functionalities. While this has worked so far, it prevents us from accessing deeper device features that are only available through native development.
By migrating the app to React Native, we could expand functionality and provide features that are not possible on the web, especially on iOS where PWAs face heavy restrictions.
Why React Native?
- Access to native APIs: Camera, microphone, push notifications, biometrics, background tasks, Bluetooth, and other system-level integrations.
- App Store compliance: Native builds are more aligned with App Store policies, while PWAs face limitations.
- Performance improvements: Ability to run features with native modules instead of being restricted to web capabilities.
- Feature expansion: Unlocking new possibilities for the app that were previously impossible with a web-only stack.
Trade-offs / Considerations
- Migration cost: Full rewrite will take time and resources.
- Code duplication: Some business logic may need to be ported/rewritten.
- Learning curve & tooling: Requires setup of RN environment, CI/CD, and handling native build pipelines (Xcode, Android Studio).
- App distribution: Moving from web to App Store/Play Store requires setting up store listings and review processes.
Next Steps
- Identify the features currently blocked by web limitations.
- Prioritize which native features would bring the most value.
- Build a small proof of concept in React Native to validate feasibility.
- Estimate migration effort and timeline before committing fully.