Germany

<p><strong>Stack</strong>: Flutter (stable), Firebase (Auth, Firestore, Storage, FCM, Crashlytics, Analytics), Google Maps (or Mapbox), Cloud Functions (Node 18).</p><p> <strong>Status</strong>: Flutter template in place (GoPool-style), Firebase connected &amp; bootstrapped. Need a dev to finish the core features to MVP.</p><h2>Goals (MVP)</h2><p>A working carpooling app (BlaBlaCar-style) for Central America with:</p><p><br></p><ul><li>Ride creation &amp; search</li><li>Seat booking with concurrency safety</li><li>Driver verification (document uploads)</li><li>In-app chat &amp; push notifications</li><li>Ratings &amp; basic admin checks</li><li>Hardened Firestore security rules &amp; analytics</li></ul><h2>Deliverables (must-have)</h2><ol><li><strong>Auth &amp; Profiles</strong></li></ol><ul><li>Firebase Auth (Email + Phone).</li><li>Profile screen: name, phone, avatar, role (driver/rider), rating, <strong>fcmToken</strong> persistence.</li></ul><ol><li><strong>Driver Verification</strong></li></ol><ul><li>Upload driver license &amp; vehicle docs → Firebase Storage.</li><li>Simple review flag (<code>users.docsStatus: pending|approved|rejected</code>).</li><li>Block ride creation if <code>docsStatus != approved</code>.</li></ul><ol><li><strong>Rides &amp; Booking</strong></li></ol><ul><li>Create ride: from/to (name + lat/lng), dateTime, pricePerSeat, seatsTotal, seatsLeft, notes.</li><li>Search rides: by date range + origin/destination text (with place autocomplete) + pagination.</li><li>Book seats: <strong>transactional</strong> decrement of <code>seatsLeft</code> (Cloud Function) to avoid race conditions.</li><li>Cancel booking (restore seatsLeft via Function), booking status history.</li></ul><ol><li><strong>Chat &amp; Push</strong></li></ol><ul><li>One chat per booking (Firestore subcollection).</li><li>FCM push for: new message, booking created/confirmed/cancelled, driver doc status changed.</li></ul><ol><li><strong>Ratings</strong></li></ol><ul><li>Post-trip: rider→driver rating 1–5 + comment; update driver’s <code>ratingAvg</code>, <code>ratingCount</code> atomically (Function).</li></ul><ol><li><strong>Maps</strong></li></ol><ul><li>Pickers for origin/destination (Google Places Autocomplete).</li><li>Show route polyline (Directions API) on ride details.</li><li>Basic distance/ETA shown.</li></ul><ol><li><strong>Security &amp; Quality</strong></li></ol><ul><li><strong>Firestore Security Rules</strong> covering users/vehicles/rides/bookings/reviews (role-based, owner checks).</li><li><strong>App Check</strong> (Play Integrity / App Attest).</li><li><strong>Crashlytics &amp; Analytics</strong> events for key flows (auth, ride_create, booking_create/cancel, message_send).</li></ul><ol><li><strong>Admin (MVP)</strong></li></ol><ul><li>Lightweight admin screen (in-app “hidden” route or Flutter web) to:</li><li class="ql-indent-1">list drivers with <code>docsStatus=pending</code>, view docs, set <code>approved/rejected</code></li><li class="ql-indent-1">search rides/bookings by date/user</li><li>Alternatively acceptable: clear admin instructions using Firebase Console + a small <strong>Cloud Function</strong> HTTP endpoint to set docs status securely (auth’d with callable functions).</li></ul><ol><li><strong>DX &amp; Handover</strong></li></ol><ul><li><code>README.md</code> with setup (dev/prod flavors, Firebase projects, API keys).</li><li>Firestore <strong>composite indexes</strong> JSON + import command.</li><li>Env separation (dev/prod) via <code>flutterfire configure</code> flavors.</li><li>Android <strong>release APK</strong> + instructions; iOS build verified for simulator (no App Store submission required).</li></ul><h2>Nice-to-have (if time permits)</h2><ul><li>Price suggestion based on distance.</li><li>Block booking conflicts (same rider overlapping time).</li><li>Simple dispute report flag on bookings.</li></ul><h2>Firestore (suggested schema)</h2><ul><li><code>users/{uid}</code>: name, phone, photoUrl, role, ratingAvg, ratingCount, docsStatus, fcmToken</li><li><code>vehicles/{id}</code>: ownerUid, brand, model, seats, plate, docsStatus</li><li><code>rides/{id}</code>: driverUid, from{name,lat,lng}, to{name,lat,lng}, dateTime, pricePerSeat, seatsTotal, seatsLeft, status(open|closed|cancelled), createdAt</li><li><code>bookings/{id}</code>: rideId, riderUid, seats, amount, status(pending|confirmed|cancelled), createdAt</li><li class="ql-indent-1"><code>bookings/{id}/messages/{msgId}</code>: fromUid, text, createdAt</li><li><code>reviews/{id}</code>: targetUid, fromUid, rideId, stars, comment, createdAt</li></ul><p><strong>Composite indexes (examples):</strong></p><p><br></p><ul><li><code>rides</code>: <code>status ASC, dateTime ASC</code></li><li><code>rides</code>: <code>status ASC, from.name ASC, dateTime ASC</code> (if filtering by origin text)</li><li> (Provide <code>firestore.indexes.json</code>.)</li></ul><h2>Security Rules (acceptance baseline)</h2><ul><li>Users: read self &amp; public fields; update only self.</li><li>Vehicles: CRUD only by <code>ownerUid</code>.</li><li>Rides: create/update/delete only by <code>driverUid</code>; read public.</li><li>Bookings: create only by <code>riderUid</code>; update by rider OR the ride’s <code>driverUid</code> (status only).</li><li>Reviews: create only after booking with <code>status=confirmed</code> &amp; <code>dateTime &lt; now()</code>; one review per pair (enforced by Function).</li></ul><h2>Cloud Functions (required)</h2><ul><li><code>bookSeats(rideId, seats)</code> → transaction: check <code>seatsLeft &gt;= seats</code> → decrement → create booking → send FCM.</li><li><code>cancelBooking(bookingId)</code> → increment ride <code>seatsLeft</code> if applicable → set status → FCM.</li><li><code>onReviewWrite</code> → recalc target user’s <code>ratingAvg</code>/<code>ratingCount</code>.</li><li><code>setDocsStatus(uid, status)</code> (callable, admin-only).</li><li><code>onMessageCreate</code> → push to the counterparty.</li></ul><h2>Testing / Acceptance Criteria</h2><ul><li>Create driver (approved) → create ride → show in search → book 1–n seats from two devices simultaneously (no oversell).</li><li>Cancel booking restores seats.</li><li>Push notifications received in foreground &amp; background.</li><li>Driver with <code>docsStatus=pending</code> <strong>cannot</strong> create rides.</li><li>Reviews only after confirmed trip; rating aggregates update.</li><li>Rules tested: unauthorized updates are <strong>denied</strong> (provide a small <code>rules-test.md</code> with 5–8 negative tests).</li></ul><h2>Code Quality</h2><ul><li>Null-safe, Flutter stable, no analyzer errors, no unused imports.</li><li>Layered structure (<code>/data</code>, <code>/domain</code>, <code>/ui</code>), providers or BLoC (dev’s choice, be consistent).</li><li>All secrets via Firebase Console; <code>.env</code>/keys excluded from VCS.</li><li>Meaningful Analytics events (<code>auth_login</code>, <code>ride_create</code>, <code>booking_create</code>, <code>booking_cancel</code>, <code>chat_message_send</code>).</li></ul><h2>What we provide</h2><ul><li>Git repo access.</li><li>Firebase projects: <strong>dev</strong> and <strong>prod</strong> (you wire with <code>flutterfire</code>).</li><li>Google APIs keys (Maps/Places/Directions).</li><li>Brand assets (app name, colors, icons).</li></ul><h2>Your application (please include)</h2><ul><li>2–3 Flutter apps live or APKs (preferably Firebase + FCM + Maps).</li><li>Short note on your preferred state management &amp; why.</li><li>Time estimate &amp; fixed price.</li><li>Start with the word <strong>CARPOOL-MVP</strong> so I know you read it.</li></ul><p><strong>Budget</strong>: Fixed-price (open to your proposal).</p><p> <strong>Timeline</strong>: MVP within ~2–3 weeks is ideal.</p>

Finish Firebase backed Carpooling App

About the Client

Useful links

Company

Information

Content Writers

Freelancers

Freelance Jobs

Online Jobs

Designers

Developers

Translations