Explain React App

• Cross-platform mobile app for iOS & Android (React / PWA; can be wrapped in React Native later).
• GPS-enabled flight logging and risk assessment capture.
• PHP REST API + MariaDB as the system of record.

Why we chose a React web app instead of an “installer” app

We wanted mobile GPS features without going through App Store / Play Store registration, fees, review times, and update delays. A React web app (PWA) launches from a simple URL or QR code, can be “installed” to the home screen, and we can ship updates instantly—no store resubmission.

Benefits for this project

• No stores, no accounts: distribute via link/QR; avoid developer program setup and review cycles.
• Instant updates: fix or add features on the server—users get them on next load.
• One codebase: same React code works on iOS, Android, and desktop—faster to build and maintain.
• GPS access in the browser: modern mobile browsers support the Geolocation API with user consent, which is enough for on-session flight logging.
• Offline-friendly: with PWA caching we can keep the UI available offline and sync when back online.
• Lower complexity/cost: simpler toolchain (React + our PHP API), fewer certificates, and less release management overhead.

Future-proofing (if we need more device access)

• Wrap later without rewriting: we can package the same React app or migrate to React Native/Expo to ship a store app when background GPS, richer sensors, or native push become must-haves.
• Hybrid approach: keep the lightweight web app for most users and a small native companion for background tracking or specialized features.

Summary: React gives us speed of delivery, easy distribution, and enough GPS to start. If requirements grow (e.g., continuous background tracking), we can step up to a wrapped or native build later.