Skip to content
NMNikolaos.
Back to projects

Engineering case study / SaaS · Full-stack

FleetRoutIQ

Multi-tenant fleet operations prototype with a FastAPI backend, GPS-enabled web dashboard and Flutter Android app.

Working local prototype · In developmentUpdated 2026-11-18
View GitHub

Product overview

FleetRoutIQ explores how a field-service organization can manage vehicles and review driver-reported locations across a web control center and an Android app. It is a working local-development prototype, not a deployed production service. The public showcase contains documentation and demonstrations rather than application source code.

Product screenshots

Web control center

FleetRoutIQ web map showing the last recorded position of demo vehicle DEMO-001
Web map: last recorded demo vehicle position, speed, status and GPS timestamp. Not proof of continuous real-time tracking.
FleetRoutIQ organization-scoped vehicle duty status dashboard
Vehicle duty status for a demonstration organization with one vehicle. The interface indicates a five-second refresh interval.

Android app

FleetRoutIQ Android app sign-in screen
Android authentication screen in the local-development prototype.
FleetRoutIQ Android work session with timer, assigned vehicle and GPS status
Active driver work session and GPS upload status; the captured screen says Waiting for GPS signal.

System architecture

FleetRoutIQ system architecture connecting Next.js, Flutter, FastAPI, Supabase Auth, PostgreSQL and Traccar
System architecture from the project's own documentation. Open for full resolution.

The Next.js dashboard and Flutter Android app use a FastAPI business API. Supabase Auth provides identity, while PostgreSQL stores organizations, memberships, vehicles, work sessions and telemetry. Traccar is a separate GPS integration with its own development database. Docker Compose orchestrates the local services; Redis is provisioned but is not evidence of completed caching or background jobs.

Functional flow

Historical FleetRoutIQ functional flow diagram from exercises 01 through 20
Historical exercise 01–20 design diagram; the web map was implemented later. An editable draw.io file is available below. Download editable diagram

The functional diagram is a historical design artifact from exercises 01–20. The web map was completed afterward; this drawing is not a claim that every depicted workflow is implemented.

Implemented in local development

Engineering decisions

Separate identity and business data

Supabase Auth manages login and tokens. A separate application PostgreSQL database stores business data. The backend must verify both user identity and membership for the selected organization; a client-provided organization identifier alone does not grant access.

Smartphone-first tracking

Using the driver's phone avoids dedicated GPS hardware in the prototype. It introduces battery, permission, network and background-execution constraints that require further validation.

Dedicated telemetry service

Traccar supports telemetry integration while FastAPI remains responsible for business authorization and organization-scoped data. Durable retries and reconciliation between forwarding and persistence are not yet implemented.

Testing and evidence

The project's historical Exercise 18 backend checkpoint recorded 112 passed, 2 skipped, 1 warning. Later development notes report successful local GPS collection, telemetry ingestion and passing tests, but the exact final count was not retained. These are historical development results, not a fresh CI run or a public source-code audit.

The screenshots document a demonstration organization and vehicle. The Android tracking screen includes a “Waiting for GPS signal” state, so it is not proof of uninterrupted background tracking. The map shows the latest known location, not continuous real-time movement.

Security and known limitations

Authentication, tenant scoping and RLS have been developed and exercised locally, but no production security audit is claimed. Remaining gates include mandatory device credential verification, trusted HTTPS for mobile traffic, review of RLS/tenant identity trust boundaries, location-data privacy and retention policies, and robust offline retry and background tracking.

The vehicle CRUD interface, complete user-facing RBAC, dispatch workflows, analytics, alerts, production deployment and iOS validation are planned or incomplete, not presented as shipped.

What comes next

Complete authorization hardening and device credential checks, improve offline GPS reliability, validate background tracking on real devices, and collect dated sanitized test evidence. The source repository remains private; this public portfolio showcases the documented system and its tradeoffs.

Contact about this projectDownload CV (PDF)