I’m ready to move from concept to a working Android-only ride-hailing application built with React Native. Both drivers and riders will use the product, so the codebase, navigation flow, and backend need to cleanly separate (and securely share) the two experiences. Core features I need implemented (or, where partially done, completed and iron-clad): • Google Maps + OpenRouteService for real-time routing • From/To address search through Google Places Autocomplete • Accurate polyline rendering with distance and duration read-outs • Dynamic driver list that shows car model, rating, next available slot, and price • Fare calculation that changes automatically for Luxury, AC, and Non-AC vehicles • Ride search updates and alert notifications so riders stay informed • Smooth screen flow between MapScreen and DisplayScreen without jarring reloads Server side, everything runs on Node.js with Express and a PostgreSQL database that stores users, rides, and bookings. Clean, well-documented REST endpoints for ride creation, booking management, and driver operations are a must. The interface should feel classic and traditional—think familiar taxi-meter aesthetics brought into a responsive, card-based layout—so pixel-perfect attention to typography, spacing, and colour hierarchy matters. Acceptance checklist before sign-off: 1. App installs and performs flawlessly on the latest two Android versions. 2. All listed features work end-to-end against a live test server. 3. API responses are validated, paginated where necessary, and return sensible error codes. 4. Database schema is delivered as migration files, fully version-controlled. 5. Source code is pushed to my private Git repository with clear README and setup scripts. If you’ve shipped production React Native apps, worked with mapping APIs, and enjoy refining classic UI details, let’s talk timing and milestones.