Bingo is a complete ride-hailing platform: a rider app, a captain app, an operations console and the server that keeps them in step. It is designed and engineered by HALO Studio, and it launches under your name, your colours and your fares, on iOS, Android and the web.
Most founders spend a year and a large budget reaching a first ride. With Bingo you start on day one of operations.
India's ride-hailing market is still expanding, and the fastest growth is in two-wheelers. The bigger change is in how platforms earn: the major players have moved captains from per-ride commission to flat subscriptions. That model favours regional operators who run lean, and Bingo is built for it.
Captains pushed back on commissions of 20% or more. In under three years every major platform has offered a zero-commission plan, where the captain pays a small daily fee and keeps the whole fare. Revenue now comes from software access rather than a cut of each trip.
For a new operator that is good news. You no longer need to outspend incumbents on incentives to win captains. A fair, flat plan and a better app can do the job, and Bingo's captain app already shows a ₹0 commission breakdown on every payment.
A ride-hailing business works only when the operator, the rider and the captain all win. We designed each app around what that person needs at that moment, drawing on public market data and on what we learned building and testing the pilot.
A founder, fleet owner, transport co-operative or regional business that knows its city and wants to own the customer relationship.
Students and young professionals on short trips, office commuters, and riders who travel late at night.
Bike, auto and cab drivers who often work across several apps and judge each by what they take home.
Two apps, a dashboard and a server, each with its own edge cases, before the first rupee of revenue.
All four parts exist, share one design system and are already tested together. You start with branding and configuration.
Spreadsheets and phone calls cannot tell you which captains are online or which rides are stuck.
The console shows revenue, live rides, captains online, cancellation rate and a live activity feed, refreshed every two seconds.
Surge pricing and "meter plus extra" disputes, especially in autos.
Every vehicle shows a fixed fare before booking. The server recalculates it from your fare table, so the app can never show one price and charge another.
Not knowing when the vehicle will arrive, who is driving, or how to get help.
A large countdown, the captain's name, rating and number plate, a four-digit ride OTP, and share trip and SOS on every in-ride screen.
Captains switch apps over a few rupees a trip.
A zero-commission plan is built in, and every payment screen shows the captain exactly what they earned.
Small buttons, accidental taps and unclear next steps.
One big action per screen, confirmed with a swipe, so a pocket tap cannot accept, arrive or end a trip.
Every ride moves through the same five states, and only the right person can move it forward. The server checks each step, so the rider app, the captain app and the console always agree on where a ride is.
Picks a drop, sees fixed fares for bike, auto and cab, and books. A ride OTP is created.
Nearby captains of that vehicle type see the request with a 15-second ring. The first swipe wins.
The rider watches the countdown and plate. The captain swipes "Arrived".
The rider reads out the code. The server checks it and never shows it to the captain.
Payment is settled (UPI, wallet or cash), then the rider rates and tips.
Creates the ride, then follows it live: captain details, arrival countdown, trip progress, receipt.
Sign-in, matching, fares, the ride rules, wallet ledger, earnings and the activity log, in one database with transactions.
Captains see requests they can take. The console sees everything and can cancel, suspend, block or change fares.
The rider and captain apps share one component library, so buttons, maps, type and motion are identical in both. These are real screens from a live test ride between the two apps.
From home screen to booked ride in three taps.
Big targets, one action per screen, every step confirmed with a swipe.
Your whole city on one screen, in a web browser.
Overview · Rides · App controls. Also included: Captains (presence, suspend) and Riders (spend, block).
Book a ride, pick the drop, confirm the vehicle. No account forms beyond a phone number and a first name.
Each screen has one primary action in one accent colour, so nobody has to hunt for the next step.
A countdown ring shows captains how long they have. Swipe to accept or tap Decline.
The right rider gets in the right vehicle, checked by the server, with no extra hardware.
Every vehicle card shows the price before booking, from the fare table you control.
Riders and captains open the app straight to home. A refused session signs out cleanly.
Once you are live, day-to-day operations happen in the web console. These are the tasks an operations manager does, in the order a new city usually needs them.
Enter base, per-km and per-minute rates for bike, auto, cab and premium. A 5 km preview shows what riders will pay. Publish, and both apps use the new table within 10 seconds.
Captains sign in with their phone, add their vehicle and number plate, and upload their licence, RC and ID. You approve them and they can go online.
Revenue, rides today, live rides, captains online, average fare and cancellation rate, each compared with yesterday at the same time, beside a live fleet map and activity feed.
Search by ride ID, rider, captain or place. Open a ride to see its route, timeline and OTP, and cancel it if needed. Both apps are told straight away.
See each captain's presence, trips and earnings, and each rider's spend and cancellations. Suspend a captain or block a rider in one click.
Publish a banner on the rider home ("Flat ₹20 off bike rides this weekend") or the captain home ("High demand near the tech park, 6 to 9 PM").
The apps and the server are all written in Dart, so the ride model, the fare rules and the API client are shared instead of duplicated. One Flutter codebase builds the native iOS and Android apps and the web console.
| Layer | What we use | Why it matters to you |
|---|---|---|
| Apps | Flutter 3.47Dart 3 | Native iOS and Android apps plus the web console from one codebase. One team, one set of fixes. |
| Design system | Shared Dart package | Colours, type, logo, buttons, swipe controls and maps live in one place. Rebranding is done once and applies to every app. |
| Server | Dart HTTP serverREST API | A single small service that is easy to host, with every rule enforced on the server and role checks on each request. |
| Database | SQLitemigrationsPostgreSQL at scale | Real SQL with constraints, indexes and transactions. The wallet is an append-only ledger, so balances always add up. |
| Security | Phone OTPSHA-256 tokensPBKDF2 | Codes expire after 5 minutes and are rate-limited. Session tokens and codes are stored only as hashes. Console passwords are salted. |
| Sync | HTTPS polling | Works on weak mobile networks and through any firewall. Live sockets can be added later for very large fleets. |
| Quality | API test suitestatic analysis | 21 automated API tests run against a real server, and every app passes Flutter's analyzer with no issues. |
| Integrations | SMSPaymentsMapsPush | Clear plug-in points for your SMS provider, payment gateway, maps and push notifications, connected during deployment. |
HALO runs the whole launch with you. This is the sequence, and who does what.
Your name, logo, colours and typeface go into the shared design system, together with app icons, splash screens and store artwork. Every screen picks them up.
Vehicle types, fare table, captain plans, payment methods, popular places, support contacts, terms and privacy policy.
SMS for sign-in codes (with DLT registration in India), a payment gateway, maps and routing, and push notifications. The accounts are in your name, so you own the relationships.
Deploy the ride server to your cloud account behind HTTPS on your domain, with daily backups, monitoring, and console users for your team. The on-screen pilot code is switched off.
Android to Google Play and iOS to the App Store, through internal testing and TestFlight first. The console goes live on the web.
Onboard a first group of captains, run test rides across the city, watch the console, tune fares, then open to riders.
Your brand on all three apps, configured for your city and running on a test server. Use it for investors, partners and a captain pilot.
Everything in the deployment plan: integrations, production server, store listings and a supported go-live.
Hosting care, updates for new iOS and Android versions, fixes, and a roadmap of new features as your city grows.
A ride-hailing service depends on a few outside services. They are billed to you directly by each provider, with no HALO mark-up. Most are pay-as-you-go, so costs stay low until rides grow.
| Item | Type | Typical providers | Indicative price | Notes |
|---|---|---|---|---|
| Apple Developer Program | Required | Apple | $99 / year | Needed to publish the iOS rider and captain apps under your company name. |
| Google Play Console | Required | $25 one-time | Needed to publish both Android apps. | |
| Cloud server and database | Required | AWS, Google Cloud, DigitalOcean, Hetzner, Azure | from ~₹1,500 / month | One small instance covers a city launch. Moving to managed PostgreSQL and a second instance adds cost as you scale. |
| Domain and HTTPS | Required | Any registrar · Let's Encrypt | ~₹1,000 / year | For the API and the console. HTTPS certificates are free. |
| SMS sign-in codes | Usage-based | MSG91, Gupshup, Twilio | ~₹0.15–0.25 / OTP | Plus 18% GST. Indian OTPs need DLT-registered sender IDs and templates, which take a day or two to approve. Charged per sign-in, not per ride. |
| Maps, search and routing | Usage-based | Google Maps Platform, Mapbox, or OpenStreetMap | free tier, then per 1,000 | Google gives a free monthly allowance on each product (10,000 calls for most Essentials products) and then charges per 1,000 calls. An OpenStreetMap stack has no per-call fee, only hosting. |
| Payment gateway | Usage-based | Razorpay, Cashfree, PayU, Stripe | ~2% / online payment | Typical standard-plan rate for cards and wallets. UPI pricing differs by provider and plan, so confirm it at sign-up. Cash rides cost nothing. |
| Push notifications | Optional | Firebase Cloud Messaging | Free | Ride updates and announcements when the app is closed. |
| Crash reporting and analytics | Optional | Firebase Crashlytics, Sentry | Free tier | Recommended from launch day. |
| HALO Orbit care plan | Optional | HALO Studio | Quoted monthly | Hosting care, store updates, fixes and new features. |
Prices are indicative, taken from providers' published rates and third-party price trackers in 2025–26, and exclude taxes unless stated. Providers change their pricing, so we confirm current rates with you during deployment. The Bingo licence and launch fee are quoted separately for each brand and city.
Tell us your city and your launch date. We'll show you Bingo running live with a real ride between the two apps, then send a fixed proposal for your launch.