How benjidev028/mova works
Project Type and Purpose
• This is a React Native mobile application (“movaNB”) for a ride-hailing service.
• The README is minimal, but the file tree shows authentication flows, separate screens for drivers (conducteur), passengers (passager), and generic user management.
• It integrates with Google Places (two components under src/composants/googleplace*).
File Structure Analysis
• Top-level:
• movaNB/App.js, index.js, app.json – React Native entry points
• movaNB/assets – static images/intro
• movaNB/src/composants – reusable components (GooglePlaceInput, etc.)
• movaNB/src/navigation – React Navigation stacks and tab navigators
• movaNB/src/screen – feature folders (authentifaction, conducteur, passager, user) each containing screen modules
• Pattern: feature-based organization (each domain area has its own folder of screens) and a clear separation of navigation versus UI components.
• No backend code here – the mobile app consumes external APIs (authentication, ride-matching, Google Places).
Key Insights from README
• Title “mova” hints at mobility/ride-sharing.
Detailed Capture
• Don’t forget the feature grouping: authentication stack vs. client stack vs. tabs
• Call out reusable component library (src/composants) as a shared module
• Sequence for a full booking flow: login → search → select route → confirm → payment → confirmation