Mobility · Booking prototype

Cabify

● Full-featured Prototype

A taxi and ride-management web application with separate user, driver and admin workflows, multiple booking types, vehicle selection and payment-oriented screens.

FlaskMySQLSQLiteBootstrapPasslibRide Booking

01 · OVERVIEW

What is Cabify?

What the project does

Cabify models a ride-hailing workflow across three sides of the platform: customers, drivers and administrators. It explores how booking requests move through availability, authorization, ride acceptance and payment-oriented screens.

How it benefits the user/business

Separates customer, driver and admin responsibilities.
Supports current, advance, shared and private booking concepts.
Provides driver authorization and ride-request workflows.
Demonstrates a multi-role backend structure for a mobility platform.

Platform & environment

Web application — Flask backend with MySQL in the main implementation and SQLite conversion for local experimentation.

02 · FEATURES

What is included?

01 · User registration and loginImplemented as part of the project's current scope.

02 · Current and advance bookingImplemented as part of the project's current scope.

03 · Shared and private ridesImplemented as part of the project's current scope.

04 · Vehicle selectionImplemented as part of the project's current scope.

05 · Pickup and drop informationImplemented as part of the project's current scope.

06 · Driver registration and authorizationImplemented as part of the project's current scope.

07 · Driver ride acceptance/rejectionImplemented as part of the project's current scope.

08 · Booking history and statusImplemented as part of the project's current scope.

09 · Payment/cash/UPI-oriented screensImplemented as part of the project's current scope.

10 · Admin driver managementImplemented as part of the project's current scope.

03 · WORKFLOW

How the project works

Customer
  ↓
Choose Ride Type
  ↓
Pickup + Drop
  ↓
Vehicle / Driver Options
  ↓
Create Booking
  ↓
Driver Availability
  ↓
Driver Accepts / Rejects
  ↓
Ride Journey
  ↓
Payment / Cash Flow
  ↓
Booking History

04 · BACKEND

What role does the backend play?

The backend/application layer is responsible for connecting the interface to the project's data, business logic and user workflows.

Session state keeps track of users, drivers and admin roles.
Booking records separate ride types such as current, advance, share and private flows.
Driver credentials and authorization are handled through backend records and views.
Admin pages support driver authorization and operational management.
The backend is responsible for moving a booking through its lifecycle rather than simply displaying a ride form.

05 · USAGE

How is it used?

Users choose a ride type, provide journey information and create a booking. Drivers have a separate workflow for viewing requests and accepting/rejecting rides, while administrators can manage driver authorization.

Project maturity: Full-featured Prototype. The purpose of this page is to explain the implementation that exists in the repository, while keeping production-readiness claims separate.

06 · LIMITATIONS

Current boundaries

This is a functional prototype rather than a production ride-hailing platform. Real-time GPS, live navigation, WebSockets, secure payment gateway processing and production identity-document storage would be needed.