How raazgupta239/iotbased-traffic-ambulance-navigation works
Project type and purpose
• From the file tree (App.js, index.js, navigation/, screens/, android/, ios/) and the README name (“ambulance-project”), this is a React Native mobile application whose purpose is to let users sign up / log in via OTP, view ambulance locations, chat with dispatch, and request ambulance services.
• Although the repository contains only the client code, the UX flows (LoginPage, VerifyOtp, HomePage, TrafficLocation, Chatbox, Dashboard) imply a backend architecture built as a suite of microservices (authentication, user profile, dispatch/dispatch-tracking, chat, notifications, external map/traffic).
File structure
• Top-level:
• App.js + index.js – application entry, root navigator and context provider
• navigation/TabNavigator.js – React Navigation setup, tab/stack definitions
• screens/… – individual UI screens implementing each flow
• userContext.js – global state management via React Context
• android/ & ios/ – native build wrappers, configuration, native modules (MainActivity, AppDelegate, splash assets)
README for additional insights
• README only gives the project name. We infer functionality from screen names:
• Login & SignUp → OTP verification
• Home & TrafficLocation → real-time map / traffic
• Chatbox → WebSocket or push chat
• Dashboard & Profile → user data, history
Detail
• React Native screen’s dependency on the API (e.g. VerifyOtp → OTP Service).
• Real-time flows (WebSocket) separately from REST calls.
• Error flows (e.g. failed authentication → retry OTP).