How emmanuelchucks/react-native-uber-clone works
Project type and purpose
• This is a cross‐platform mobile application (React Native + Expo) that clones core Uber features: selecting origin/destination, viewing rides, estimating fare and travel time.
• There is no custom backend; the app talks directly to external mapping / routing APIs (e.g., Google Maps, Directions, Places).
File structure
• Top‐level:
• App.tsx – entry point
• app/ – Redux setup (store.ts, hooks.ts) and navigationSlice.ts for global state (origin, destination, travelTimeInformation)
• components/ – reusable UI building blocks (Map, NavOptions, NavigateCard, RideOptionsCard, etc.)
• screens/ – three main screens (HomeScreen, EatsScreen, MapScreen)
• assets/ – images and screenshots
• config files – babel.config.js, tsconfig.json, app.json, env.d.ts
• Patterns:
• A single‐page mobile app with React Navigation handling screen transitions
• Redux Toolkit for state management (MVC‐light pattern: components dispatch actions, selectors read state)
• API calls for distance/time estimation and map rendering lives inside Map.tsx and slices (not shown, but implied)
Key details from the README
• Cross‐platform support (iOS, Android, Web) via Expo
• Features: pick origin/destination, choose ride type, calculate fare/time
• No mention of a proprietary backend – relies on remote services
Detailed capture of essential elements
• Every screen name and major component in the UI layer
• NavigationSlice and store.ts as the single source of truth