Ride & Bite - Flutter Ride Hailing, Food & Parcel Delivery App with Admin & API

Launch a ride-hailing, food delivery and courier marketplace

Ride & Bite is a complete, editable Flutter source project for an on-demand marketplace: a customer super app, a merchant workspace, a driver partner app, a web operations console and the Dart API that powers all of them. Rebrand it, connect your own payment and map accounts, and you start from a working product instead of a blank screen.

Live demo: https://showcase.rideandbitepro.cloud/ — customer, ride booking, food, parcel, merchant, driver and admin surfaces, with one-tap demo logins.

What is included

• Customer app — book rides on a live map with itemised fares before confirming, order food with cart and checkout, send parcels, follow order status, manage wallet and promotions.
• Merchant app — live order board with accept, prepare and hand-over, menu and stock editing, store hours, promotions, earnings and payouts per outlet.
• Driver app — offer feed showing payout, pickup distance and drop-off before accepting, online/offline, trip stepper, hand-over confirmation, earnings and acceptance rate.
• Web operations console — live operations board, dispatch, refunds, customer tickets, merchant catalogue and onboarding, pricing and promotions, revenue and audit history.
• Dart API — role-scoped permissions, idempotent checkout, rate limiting, health and readiness probes, structured JSON logs and an OpenAPI 3.1 contract.
• Deployment kit — Docker Compose, API and web Dockerfiles, reverse-proxy (nginx and Caddy) configuration, a deploy script and smoke checks.
• Documentation — a self-contained offline HTML manual plus setup, architecture, API, deployment, iOS build and rebranding guides.

Built for real operations

• Fare engine — base, distance, time, surge and night multipliers, minimum fare, booking fee, tolls and promotions, returned as an itemised quote.
• Surge engine — demand ratio snapped to published multiplier buckets, with a cap so pricing stays explainable.
• ETA engine — road-detour and traffic-band aware travel and pickup estimates instead of straight-line guesses.
• Driver dispatch — weighted ranking across proximity, acceptance rate, rating and fairness, so assignments can be justified to drivers.
• Promotions — percentage, flat, free-delivery and waived-fee offers with caps, minimums, validity windows, first-order rules and usage limits.
• Money — integer-cent arithmetic and an append-only wallet ledger with running balances, pending holds, idempotency keys and reversals. No floating-point drift.
• Order lifecycle — one shared rulebook for rides, food and parcels, so an illegal status change can never render a button.
• Accounts — PBKDF2-HMAC-SHA256 password hashing, OTPs with TTL and attempt limits, session tokens and lockout. Cards are tokenised; no card number or CVV is stored.

Three apps, one codebase

The customer, merchant and driver apps share one Flutter project with separate application IDs, names and launcher icons, so all three install side by side on one phone. Pricing, lifecycle and money rules come from the same domain layer that the API imports — the app and the server cannot disagree about what a trip costs.

Platform behaviour follows the native convention on each side: Material transitions, ripple and clamped scrolling on Android; Cupertino slide, interactive back swipe and rubber-band scrolling on iOS. Android release signing is wired through key.properties.

Requirements

• Flutter 3.38+ with Dart 3.10+ (workspace layout — run flutter pub get at the repository root).
• Android SDK 35 for the Android builds; Xcode 15+ on macOS for iOS.
• Docker and Docker Compose for the one-command web + API deployment.
• Any OpenStreetMap-compatible tile provider. A MAP_TILE_URL build define switches providers without a code change.

What you connect yourself

These are deliberate integration points with documented adapters and environment variables — no private keys, payment credentials, signing certificates or commercial map licences are bundled:

• Payment gateway for card and wallet top-ups (the domain already models tokenised cards and refunds).
• Email and SMS provider for OTP delivery.
• Push notifications.
• A licensed tile and geocoding host for production traffic.
• A production database and object storage for your hosting provider.
• App Store and Play Store signing for your own publisher accounts.

Two-minute local start

docker compose up -d --build — then open the web console, sign in with the demo administrator account documented in the manual, and every surface is reachable from the same build.

Documentation

The archive includes Ride-and-Bite-Documentation.html, a single self-contained manual that opens in any browser without an internet connection: installation, environment variables, renaming and branding, application IDs, launcher icons, API keys, folder structure, deployment and credits. Alongside it: README, ARCHITECTURE, API, ADMIN_PANEL, DEPLOYMENT, DEMO_GUIDE, IOS_BUILD, RELEASE, REBRANDING, INTEGRATIONS, CREDITS, ROADMAP and a scorecard that states the known limits honestly.

Market focus

Written for teams launching in Europe first, and structured so the same codebase can be adapted to the UK, US, Canada, UAE and Saudi Arabia. Currency, tax, address format, language, payment method and consumer-law requirements differ per market and are part of your own launch work — the source gives you the engines, not a pre-approved legal wrapper for any country.

Quality

• 511 Flutter tests and 40 API tests passing on the packaged commit.
• flutter analyze reports no issues.
• CI builds all three Android variants and the iOS project on every push.

Support

Questions about the built-in features, setup of the bundled stack, and bug fixes are included. Customisation, new features, third-party account setup (payment, SMS, maps, stores) and market-specific legal or compliance work are outside item support.

Scope

This is editable source code, not a hosted service, a store-ready binary or a turnkey licensed transport or payment operation. The public demo uses seeded, disposable data and resets — never reuse demo credentials in production. Buyers complete production integrations and their own legal, tax, privacy, insurance, food-safety and transport reviews before launch.