Case study / 03

Full Stack / Fleet Technology / Web / Android

Carpool — Internal Ride and Fleet Management System

Carpool is a complete internal ride-request and fleet-management system that I developed from backend to frontend, including its Android application and integration with the Venus API.

Role

End-to-end system development covering the backend, web frontend, Venus API integration and Android application.

Focus

React, TypeScript, Tailwind CSS, NestJS

Visit live project

Carpool secure sign-in screen explaining request tracking and fleet visibility

Overview

Carpool is a modern Uber-style ride-management system built specifically for internal organisations—not a public ride-hailing marketplace. Staff request transport using vehicles owned or managed by the organisation; authorised teams review requests, assign drivers and vehicles, monitor trips and retain trip information for reporting. I developed the complete backend, web frontend and Android application, including integration with the Venus API for organisational fleet data.

Developed end-to-end, from backend services to web and Android interfaces.

Integrated with the Venus API to display and use organisational fleet vehicles.

My role

Complete system development
Product planning and UI/UX design
Backend and API development
Database design
Web frontend development
Android mobile application development
Venus API and fleet-data integration
Authentication and user-role workflows
Ride-request and approval workflows
Driver and vehicle assignment
Trip-management interface
Responsive dashboard development
Mobile application interface development

Technology

Product thinking

The challenge

What needed to become clearer.

Organisational transport is often coordinated through calls and messages, leaving request state, approvals, assignment and trip progress difficult to follow. The system needed to connect staff, managers, administrators, dispatchers and drivers while using the organisation’s existing fleet infrastructure.

The approach

How the product took shape.

I planned and developed Carpool as one full-stack workflow across backend services, database logic, web coordination tools and a native Android application. Each request becomes a traceable lifecycle, while the Venus API supplies organisational vehicle data and telematics context.

•

User roles

A controlled workflow with clear responsibility.

01Staff member

02Manager

03Administrator

04Dispatcher

05Driver

•

Product concept

An Uber-style experience for a controlled organisational fleet.

Carpool borrows the clarity of modern ride products but applies it to internal transport. Vehicles belong to or are managed by the organisation, requests follow approval policy, and authorised operational users control assignment and trip progress.

•

Full-stack role

One system developed from database logic to Android interaction.

I developed the backend services, API surface, database model, responsive React dashboard and Kotlin/Jetpack Compose Android application. Authentication, role logic, request state, assignment and fleet-data integration were designed as one connected product.

•

Backend, database and spatial logic

Ride state and fleet context share a reliable operational model.

NestJS services coordinate users, requests, approvals, trips and assignment. PostgreSQL stores the operational model, PostGIS supports location-aware data, and Redis supports fast-changing application state where appropriate.

•

Venus API integration

Organisational vehicles flow into the ride-management system.

Carpool connects to the Venus API to retrieve and display relevant organisational vehicles and fleet information. This keeps ride assignment connected to existing fleet and telematics infrastructure instead of creating a duplicate vehicle source.

•

Web dashboard and assignment

Coordination tools for approvers, administrators and dispatchers.

The responsive web interface supports request review, approval or rejection, vehicle and driver assignment, request history and fleet visibility. Status is visible as a sequence so the next responsible action is clear.

•

Android application and trip monitoring

Operational access continues away from the desk.

The native Android experience uses Kotlin and Jetpack Compose to bring request queues, fleet information, notifications and trip states to mobile users. Touch-friendly layouts preserve the same roles and operational language as the web system.

•

Responsive design

The right density for dashboard and phone contexts.

Desktop screens prioritise coordination, broad fleet context and multi-column information. Mobile screens reduce that density into focused queues, alerts, trip details and primary actions without changing the underlying workflow.

•

Workflow

Connected workflow

Internal ride-request lifecycle

01Request created

02Pending review

03Approved

04Vehicle and driver assigned

05Driver receives trip

06Trip starts

07Trip monitored

08Trip completed

Secondary statesRejectedCancelled

System design

Architecture overview

Complete internal mobility architecture

01Web Dashboard + Android Application

02NestJS API

03Authentication and Role Management

04Ride and Trip Services

05PostgreSQL / PostGIS / Redis

06Venus API

07Vehicle and Fleet Data

08Traccar Cloud / Telematics

Key features

Built around the work people need to do.

01Staff ride requests
02Manager approval and rejection
03Vehicle and driver assignment
04Driver trip receipt and status
05Live trip monitoring
06Trip completion and reporting information
07Authentication and role-based workflows
08Venus fleet-vehicle integration
09Web and native Android interfaces

Selected screens

Interface, in context.

Open any screen to inspect the interface at a larger scale.

Project value

Outcome

Carpool turns internal transport coordination into a shared, traceable system across requesters, approvers, dispatchers and drivers. Its value comes from joining complete web, backend and Android experiences to the organisation’s existing Venus fleet data—not from acting as a public marketplace.