Develop Custom TukTuk Ride-Hailing Mobile Application

Project Title:
Build an Ultra-Lightweight Ride-Hailing App (TukTuk / Auto Rickshaw Service) Optimized for Low-End Devices, Low-Bandwidth, with Voice-Location & Fare Bidding Features.
1. Project Overview
We are looking for an expert mobile app development team or senior full-stack freelancer to build a custom ride-hailing application tailored specifically for TukTuk (Auto Rickshaw) transport services.
The system consists of three main parts:
Customer App (Android & iOS) - Highly optimized for low-end hardware.
Driver App (Android only) - Ultra-simplified and lightweight.
Admin Web Panel (For system management and landmark configurations)
2. Core Architectural Constraints (High Priority)
The core value of this app is its adaptation to low-spec hardware and weak infrastructure. The winning bidder must adhere to the following constraints:
Low-End Device Optimization: The apps must run smoothly on low-spec smartphones (1GB to 2GB RAM) and older Android versions without causing device lag or high battery drain. The UI must be clean, simple, and free of heavy animations.
Low-Bandwidth & Data Saving: The app will be heavily used in areas with weak 2G/3G/4G networks and by users with limited internet data packages. API responses must be minimal, and local caching should be utilized.
Minimal Installation Size: The final APK size must be optimized and kept as small as possible to fit low-storage devices.
3. Critical & Unique Features
A. Voice-Guided Location Booking (Anti-Map Feature)
The Challenge: GPS and mapping services (like Google Maps) are highly inaccurate in informal areas, slums, and narrow alleys.
The Solution: The app must feature a prominent, easy-to-use Voice Recording Button on the main screen.
Customers can tap and hold to record a short audio message stating where they are standing and where they want to go .
Technical Requirement: The audio must be highly compressed locally (e.g., AMR or AAC formats) so it uploads instantly even on a 2G connection without consuming the user's internet bundle.
B. Landmark-Based Dropdown Booking
An alternative/complementary booking method where the user can choose their pickup or drop-off point from a categorized dropdown list of popular local landmarks (e.g., Main Square, Specific Pharmacies, Train Station, Famous Mosques/Churches). This eliminates the need to load interactive maps.
C. Fare Bidding / Negotiation Model (Like inDrive)
Instead of automatic algorithm pricing, the customer proposes a starting price for the trip.
Nearby drivers receive the request, listen to the voice note (or see the landmarks), and can either accept the price or counter-offer with a higher bid.
The customer sees all driver offers and chooses based on price, rating, or proximity.
D. Direct Peer-to-Peer Payment via QR Code
To keep the app commission-free, drivers can upload their local digital wallet QR codes (Similar to UPI / Paytm in India, or Vodafone Cash / InstaPay in Egypt).
At the end of the ride, the driver's QR code is displayed on the screen for the customer to scan and pay directly from wallet to wallet.
4. Standard App Features
Customer App: Mobile OTP signup, Active ride tracking (basic/text or lightweight map), Ride history, and an SOS Panic Button that sends an automated SMS with location to emergency contacts.
Driver App: Ultra-simple interface with large, color-coded buttons (Green to Accept, Red to Reject). The customer’s voice note must auto-play or play with a single tap. Easy profile setup with document upload for admin approval (License, National ID, Vehicle pictures).
Admin Web Panel: Comprehensive dashboard to approve/block drivers, manage the predefined "Local Landmarks" list, monitor active trips, and review user feedback.
5. Preferred Tech Stack
Frontend: Cross-platform (Flutter or React Native) optimized for lightweight builds.
Backend: Highly efficient, low-overhead backend (Node.js, Python, or Go).
Database: MongoDB, PostgreSQL, or a lightweight setup using Supabase/Firebase.
6. Proposal Requirements
When submitting your proposal, please answer the following questions:
1. Provide links/cases of previous ride-hailing or on-demand delivery apps you have successfully deployed.
2. How do you plan to technically achieve the local audio compression requirement for instant upload?
3. What framework/tactics will you use to guarantee the application runs flawlessly on 1GB RAM smartphones?
4. What is your estimated timeline and milestone-based budget for 100% full Source Code ownership and IP handover? Show More