One platform.
Rides, food and parcels — four apps that sell.
A complete marketplace in one codebase: the customer app, the merchant kitchen console, the driver partner app and a web operations control plane — backed by a Dart API with real pricing, dispatch, wallet and permission logic.
No sign-up, no install required to look around — the demo below is the shipped build.
Try every surface in a real device viewport
Pick a phone — iPhone or any Android model — and the app re-renders at that exact screen size. On a laptop or desktop the preview stays phone-sized on purpose, so you are judging the product, not a stretched canvas. The admin console opens in a desktop frame instead.
Every preview is the real deployment at rideandbitepro.rideandbitepro.cloud — the same build the APKs ship, not a video or a set of images.
16 captures of the release build
Captured from the running release build at true device resolution — no mockups, no composited UI, no stock photography. Click any screen to open it full size.
The package a buyer actually receives
Not a UI kit with placeholder screens: the engines, the API, the permission model and the deployment assets are all in the download.
Four Flutter surfaces
Customer, merchant and driver apps share one codebase with separate entry points, ids, icons and names — all three install side by side.
- Android, iOS and web targets
- Web-only admin control plane
- Responsive from 320 px up
Dart API + OpenAPI 3.1
A pure-Dart shelf service that imports the app's own domain, so pricing and order rules cannot drift between client and server.
- Sessions, roles, idempotent checkout
- Crash-safe snapshot persistence
- Health and readiness probes
Admin control plane
Fourteen operations workspaces: live map, dispatch, fleet, catalogue, support, KYC, finance, campaigns, content and app control.
- Role-scoped navigation
- Append-only audit trail
- Versioned app config with rollback
Release APKs
Three installable demo builds, one per app, with checksums alongside. iOS builds from the included Runner project with your own signing.
Deployment assets
Dockerfiles for the API and the Flutter web bundle, Compose overlays, nginx configs, a Caddy TLS edge and a smoke-test script.
Documentation
Install walkthrough, API reference, deployment guide, demo script, marketplace listing copy and the screenshot kit used on this page.
Real product logic, not a screensaver
Money is integer cents, prices come from engines, and the API decides permissions. The parts a marketplace reviewer checks first are the parts that are actually built.
| Engine | What it does in the product |
|---|---|
| FareEngine | Base, distance, time, surge, night multiplier, minimum fare, booking fee, tolls and promotions — itemised quotes. |
| SurgeEngine | Demand ratio snapped to published multiplier buckets, capped per zone. |
| EtaEngine | Road-detour and traffic-band aware pickup and travel estimates. |
| DispatchEngine | Weighted driver ranking: proximity, acceptance, rating, fairness. |
| PromoEngine | Percentage, flat, free-delivery and waived-fee codes with caps, minimums and usage limits. |
| WalletLedger | Append-only ledger with running balances, pending holds, idempotency and reversals. |
| Permissions | 25 server-enforced permissions across four roles; merchant, driver and customer data is scoped per resource. |
| Persistence | Crash-safe JSON snapshot: temp file, backup, atomic rename, quarantine on corruption, restore on boot. |
Demo accounts
The public deployment is seeded with a demo marketplace. Sign-in behaviour differs by surface: the admin console checks the active roster by email, the API accounts use a password. Click any value to copy it.
| Surface | Sign in with | Password | What you can do |
|---|---|---|---|
| Admin web console ?view=admin |
ayesha.siddiqui@rideandbite.pro
|
roster email — no password | Super-admin view: dispatch, support, KYC, finance, campaigns, app config |
| API · admin |
admin@rideandbite.dev
|
admin1234
|
Role-scoped REST access to every order, quote and audit entry |
| Merchant app |
merchant@rideandbite.dev
|
merchant1234
|
Biryani Bros storefront, menu, stock and live order board |
| Customer app |
customer@rideandbite.dev
|
customer1234
|
Browse, cart, checkout, wallet, ride and parcel booking |
| Driver app |
driver@rideandbite.dev
|
driver1234
|
Offers, active trip, trip chat, earnings and payouts |
Run the apps on a real phone
Release APKs built from this exact source — three separate apps, three icons, all installable side by side. No store account needed.
Ride & Bite Merchant
Kitchen console — storefront, sections, menu items, stock and order board.
Download APKRide & Bite Driver
Partner app — offers, trips, trip chat, earnings and daily payouts.
Download APKflutter build ipa --release. An installable .ipa cannot be offered
here because Apple signs every build with the publisher's own certificate — the buyer
signs with theirs.
Before you buy
Is this a template or a running product?
Both in the sense that matters: it is a complete Flutter project you can rebrand, and it runs end to end — pricing engines, an API with sessions and roles, three installable apps and an admin console. The screenshots and the preview on this page are the shipped build, not a design mockup.
Which versions does it need?
Flutter 3.38 or newer with Dart 3. The API is pure Dart (shelf) and runs with the same SDK. Android builds use the included Gradle setup; iOS builds with Xcode 15+ and your own signing identity.
Do I need API keys to run it?
Not for the demo. Maps use OpenStreetMap's keyless raster tiles, and the seeded data runs locally. To go live you will add a licensed tile provider, SMS/OTP, a payment gateway and push credentials — the integration points are documented.
How hard is rebranding?
Colours, type, logo, app names, bundle ids, currency and city defaults are centralised in the design tokens and build configuration. The three Android flavours and iOS bundle ids are already separated, and the launcher icons regenerate from one source image.
What is deliberately not included?
Live payment capture, production SMS delivery, push notifications and multi-instance Postgres are integration seams, not finished features. The API ships a mask-only card model, idempotent checkout and a wallet ledger; wiring a gateway is a documented step, not a rewrite.
Does the price include updates and support?
Item support and the update policy follow the marketplace listing terms. The package includes the install guide, API reference, deployment runbook and the demo script so a developer can take it from download to deployed without guessing.
Ship a marketplace, not a mockup.
Four apps, one backend and the deployment assets — ready to rebrand for your city, your currency and your brand.