Android Taxi Booking App Development

₹1500-12500 INR

Posted 1 minute ago

•

Ends in 6 days

₹1500-12500 INR

Paid on delivery

I want to launch a straightforward ride-hailing service focused on on-demand trips only—no advance scheduling, no airport-specific extras. The passenger side should let users request a ride immediately, follow the driver on a live map, and pay exclusively by card or another in-app method such as Google Pay or a payment gateway you recommend. Cash handling will not be part of this build. Drivers will have a separate interface of their own, where they receive and accept nearby requests, view the fastest route in Google Maps, and receive earnings summaries that reflect only cash-free payments. There is no third “admin” or “company” area in scope; I simply need two lean, reliable Android builds that talk to the same real-time backend (Firebase, Supabase, or something comparably scalable—open to your suggestion). To keep the project concrete, here is what I expect to receive: • Passenger APK + source • Driver APK + source • Shared backend with real-time dispatch, fare calculation, and card/online payment processing fully tested • A brief hand-off document covering environment setup and store-ready build steps If you have shipped similar ride-sharing products, especially those restricted to cash-free payments, let me know—the closer your past work is to this flow, the faster we can move.

Project ID: 40830417

About the project

5 proposals

Open for bidding

Remote project

Active 13 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

5 freelancers are bidding on average ₹7,630 INR for this job

User Avatar
Flag of INDIA

The critical part of this service is keeping the passenger’s trip, driver acceptance, live location, fare, and cash-free payment in sync across two separate Android apps. A shared backend needs to be the source of truth for dispatch and trip status, so a delayed update or interrupted connection doesn’t leave either user unsure whether a ride is active or paid. I’d build the passenger and driver interfaces as native Kotlin apps, with clear separation between screen state and backend trip state. The passenger flow would cover requesting an immediate ride, tracking the assigned driver, and completing an in-app payment; the driver flow would handle nearby requests, acceptance, Google Maps routing, and cash-free earnings summaries. Realtime backend events would drive dispatch and location updates, while server-side fare calculation and payment confirmation help keep trip records and earnings consistent. Stripe is a possible payment option, including Google Pay where supported, but the final choice should suit your operating region and payment account. I’d keep the two apps focused on their respective roles while sharing the same backend rules for trip status, fares, and payment outcomes. I’ll account for loading, failed-payment, connection-loss, and empty-request states, and check that location and map behavior remain usable during an active trip. The deliverables would include both APKs and source code, the tested shared backend, and concise setup and store-build handoff notes. Changes and technical decisions can be kept clear in the project’s Git history so the code remains straightforward to maintain. Which launch country and payment account region should the payment integration target?

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

用 HomepageTab 新标签页关注 RSS,打开浏览器就能看到更新。

安装 HomepageTab