case study / system 01

Parking Management Platform

A web, mobile and backend ecosystem for managing parking facilities, bookings, occupancy and payments through a shared API.

Web demo available Full Stack UTP · 2025
architecture / parking.sysstable view
WEB
Next.js
API REST
Node / Express
MOBILE
React Native
JWT
roles
SUPABASE
PostgreSQL
Vercel
deploy
01 / context

From an operational need to a connected system

The challenge was to coordinate parking operations across locations: facility management, space availability, bookings, vehicle entry and exit, payments and communication with customers. The system needed to serve administrative staff and mobile users without duplicating business logic.

3repositories forming one system
2main client types
1shared API at the core

Users and scope

Administrators manage parking facilities, employees, rates and operations. Customers check availability, book spaces and view their information through the mobile app. The web dashboard handles operations, while the mobile app supports the customer journey.

02 / solution

One backend core for multiple experiences

Operations management

Parking facilities, spaces, rates, employees, users and operational statuses through the admin dashboard.

Bookings and occupancy

Workflows for checking availability, creating bookings, recording entry and exit, and tracking statuses.

Payments and receipts

Models and routes for payments, payment methods, digital receipts and transaction traceability.

Notifications

The backend includes provisions for notifications and email services as the system evolves.

03 / architecture

Separation by client and responsibility

The platform consists of three related repositories. The backend handles authentication, business rules, migrations and persistence; each client consumes its endpoints according to its usage context.

front-web-parking   Next.js + TypeScript + Tailwind
          │
          ├── Axios / auth guard / role-based UI
          │
api-nodejs-parking   Node.js + Express + JWT
          │
          ├── controllers / routes / services / jobs
          ├── migrations / RLS / SQL verification
          │
front-movil          React Native + TypeScript
          │
          └── auth / maps / reservations / user flows

Supabase / PostgreSQL  relational persistence + managed service
Node.jsExpressNext.jsReact NativeTypeScriptSupabasePostgreSQLJWTVercel
04 / decisions

Key technical decisions

  • A shared API avoids duplicating rules between the web dashboard and mobile application.
  • The relational model represents relationships between users, parking facilities, spaces, bookings, occupancy, payments and receipts.
  • Versioned SQL migrations document schema changes and policy fixes.
  • Separating clients lets each experience evolve without making the backend dependent on the interface.
  • Environment variables keep local, testing and deployment configurations separate.

My contribution

I worked on the evolution and integration of the ecosystem's public repositories, connecting the backend to the web and mobile clients and documenting changes to data and operational workflows.

05 / workflow

AI as an engineering tool

Development followed an AI-assisted workflow for requirements analysis, exploring alternatives, implementation, debugging and documentation. The clearest public evidence is the versioned GitHub Copilot instructions in the backend and mobile application.

Persistent context

Repository instructions help preserve conventions and technical context as the project evolves.

Technical responsibility

AI accelerated the workflow, while decisions, reviews and functional validation remained my responsibility.

06 / evidence

Validation, deployment and limitations

  • The repository includes verification documentation, test scripts and migrations to reproduce backend changes.
  • The web dashboard has a public demo deployed on Vercel.
  • Supabase/PostgreSQL is used as a managed service, with configuration handled through environment variables.
  • My experience includes deploying the API on Azure, but the historical repository synchronization workflow is not currently available as public evidence.
  • I do not present Docker, Kubernetes, Terraform or observability as skills demonstrated by this project, because the reviewed repositories do not provide enough public evidence.
07 / roadmap

Next steps

The next stage is to consolidate an OpenAPI specification, expand automated testing, document the deployment workflow and make the boundaries between operations, bookings and billing clearer.