Zye Ride-Hailing App — Pending Tasks for Flutter Developer (Estimation Document) This document outlines the remaining tasks for the Zye Consumer App and Zye Driver App. The selected freelancer will review these items, understand the flows, and provide accurate effort estimates. 1. Book Auto – “Searching” Animation Description Implement a smooth, modern "Searching for Auto" animation when the user books an auto (Similar to Cab). This should include: • Driver icon rotation / shimmer • Map dimming effect (optional) Expected Output A polished searching animation that runs until a driver accepts/cancels the request. 2. Cancel Booking (Auto/Cab) – “Are You Sure?” Popup Description When the user attempts to cancel a booking (Auto or Cab), display a confirmation popup. Requirements • Popup should match app theme • Two buttons: Yes, Cancel and No, Go Back • Notify backend only when user confirms 3. Driver Registration – Vehicle Type Bug Fixes Description Fix issues in the driver registration flow related to vehicle type selection. Known Problems • Vehicle type not updating correctly in form • Validation issues • Incorrect API payload mapping Expected Output A fully functional driver onboarding flow with correct vehicle type mapping. 4. Driver App — In-Progress Ride: "End Trip" Button Fix Issue The “End Trip” button in driver in-progress ride screen is wrongly positioned or partially hidden. Requirement • Fix UI alignment • Ensure button is sticky & accessible • Test across small/medium/large devices 5. Background Service for Ongoing Ride (Driver + Consumer App) Description Create a background service to ensure essential tracking and ride updates continue even when app goes to background. Requirements • Runs in both Consumer and Driver apps • Periodically sends location + ride state to backend • Works on Android foreground service mode • Should not be battery-heavy • Must handle app kill / restart gracefully 6. Invoice Generation & Payment API Integration Description Integrate invoice generation and payment confirmation at the end of a ride. Requirements • Consume backend Invoice API (provided) • Display invoice summary in UX • Integrate payment processing flow (API-based) • Handle success/failure states • Update ride history accordingly 7. ETA Fix on Consumer App + Accurate Distance to Backend Issues • ETA (Estimated Time of Arrival) shown to users is often incorrect • Distance calculation sent to backend is not matching Google Maps values Task • Recalculate ETA using Google Distance Matrix API • Fetch accurate travel distance • Ensure backend receives exact distance (in meters) • Update estimation logic on UI 8. Live Nearby Driver Movement During Search Description When searching for a ride, nearby drivers should move smoothly on the map as their real positions update. Requirements • Subscribe to driver location updates (WebSocket/API) • Animate driver markers on map • Smooth transition between coordinates (avoid jumpiness) • Update at reasonable intervals (2–3 seconds) 9. Auto-Launch Google Maps Navigation After Ride Starts When driver verifies the PIN and ride officially begins: • Automatically open Google Maps in navigation mode • Starting point = Driver’s location (source) • Destination = User’s drop location • Ensure correct deep linking / intents on Android • Return back to app when navigation ends or on back press 10. Minor UI Improvements + State Management Updates Description General polishing around UI/UX and state management in both apps. Includes • Fix inconsistent paddings/margins • Resolve minor color/theme mismatches • Cleanup/optimize Provider/Bloc/StateNotifier logic • Improve screen transitions • Code cleanup (optional, if time allows) Additional Notes for Estimation Please include in your estimate: • Time required per task • Any dependencies or blockers • Assumptions you are making • Whether you need backend API details • Whether anything requires redesign • Optional improvements if time allows What We Will Provide • Full project access (after NDA) • API documentation • Screenshots / Figma references • Direct communication with founder • Backend team support for API clarifications