Integral Valet

Role
Full-stack developer
Built with
Type
Valet & car-wash platform
Integral Valet, cover

Screens

  • Integral Valet, screen 1 of 10
  • Integral Valet, screen 3 of 10
  • Integral Valet, screen 5 of 10
  • Integral Valet, screen 7 of 10
  • Integral Valet, screen 9 of 10
  • Integral Valet, screen 2 of 10
  • Integral Valet, screen 4 of 10
  • Integral Valet, screen 6 of 10
  • Integral Valet, screen 8 of 10
  • Integral Valet, screen 10 of 10

A valet-parking and car-wash subscription platform for residential and commercial buildings, delivered as one Laravel API serving a Nuxt 3 admin dashboard and an Expo member app.

Role: Full-stack developer, 17 of 63 commits (about 27%), about 1.5 months.

Helped design and build a valet-parking and car-wash subscription platform for residential and commercial buildings. Operators manage buildings, members and subscription plans; members subscribe their vehicles and book on-demand valet or car-wash appointments; building workers fulfil jobs from a role-scoped dispatch queue. Delivered as a Laravel REST API serving two clients, a Nuxt 3 web admin dashboard and an Expo (React Native) member mobile app, from one shared back end.

What I delivered

  • Laravel 10 REST API with token auth (Sanctum) and a four-role RBAC layer (super-admin, admin, worker, member) through Spatie Permission, enforced at route, ownership and building-scope levels.
  • Building and vehicle management: CRUD for buildings, members and cars, many-to-many car ownership, and per-car subscription tracking (start and end, paid status, parking number) with audit logging.
  • Subscription plans with per-building pricing: plans define a monthly car-wash quota and extra-wash pricing, and each building sets its own price per plan.
  • Appointment booking engine: valet and car-wash bookings with server-side enforcement of ownership, active subscription window, payment status and monthly wash-quota limits, with ticket-number generation and an urgent-request flag.
  • Worker dispatch panel: building-scoped appointment queue with a status lifecycle (pending → accepted → in progress → completed or cancelled), gated to each worker's assigned building.
  • Analytics dashboard: role-aware KPIs (buildings, members, employees, cars, appointments today and this week), status breakdowns, active and expiring subscriptions, recent activity, with 60-second response caching and Chart.js doughnut and line charts.
  • Nuxt 3 / Vue 3 SPA: public marketing site plus a role-gated admin dashboard, global route-guard middleware that sends each role to its home area, modal-driven CRUD with reusable data-table and pagination components, VeeValidate and Yup form validation, and an Axios client with bearer-token and 401/419 auto-logout interceptors.
  • Expo / React Native member app: animated splash with token restore, member-only login gate, "My cars" list, a date and time booking drawer, upcoming versus history appointment views with cancel and mark-urgent, profile editing, and Google Maps deep-link directions. Redux Toolkit state with AsyncStorage token persistence.
  • Real-time dispatch groundwork: an appointment-created broadcast event on a per-building channel, fired on booking to feed a live worker board.
  • Swagger/OpenAPI-documented endpoints (L5-Swagger).

Scale: Laravel API with 7 controllers, 8 models, 22 migrations (about 13 domain tables), 38 endpoints and about 2,800 lines of PHP. Nuxt web with 16 pages, 17 components and 3 Pinia stores, about 6,600 lines. Expo mobile with 7 screens and 10 components, about 3,375 lines. About 12,800 lines in total across a three-app monorepo.

Stack

  • Laravel 10
  • PHP 8.2
  • MySQL
  • Laravel Sanctum
  • Spatie Laravel-Permission
  • L5-Swagger
  • Nuxt 3
  • Vue 3
  • Pinia
  • Bootstrap 5
  • VeeValidate + Yup
  • Chart.js
  • Axios
  • SweetAlert2
  • Expo SDK 54
  • React Native 0.81
  • Expo Router
  • Redux Toolkit
  • TypeScript