Aqib Ali Ghumro
> BACK_TO_SYSTEMS
Mobile[SYS_ID: HAIRZONE]

HairZone

React Native barber-booking application backed by a modular Express and TypeScript API for customer, business, appointment, payment, media, and administrative workflows.

01.System Interface & Screenshots

Full-Stack Mobile Developer
HairZone Interface Screenshot
[SCREENSHOT_01_ACTIVE]

02. Project architecture visualization

Interactive visualization of the implemented booking flow

A React Native booking flow covering customer profiles, services, appointments, payments, notifications, maps, and administration. [This visualization reflects the implemented mobile workflow and does not imply live monitoring.]

Speed:
React Native App
Authentication
Express REST API
Business and Service Logic
Appointment Logic
MongoDB
Stripe Payments
Cloudinary Media
Notifications
Response to Mobile App
Active Pipeline Stage
Launch simulation to view stage details.
Live Stage Data Payload
Data telemetry will load here.
Console Logs
|
>Ready to trace workflow pipelines...

03. The Problem

Local barber businesses need a clearer way to manage bookings, profiles, payments, and operational visibility on mobile.

04. The Solution

Built mobile booking flows around a layered API architecture with route, controller, service, repository, and Prisma data-access layers, plus storage, payment, notification, scheduling, and admin workflows.

05. Key Features

  • >Authentication
  • >Customer profiles
  • >Business and barber profiles
  • >Categories and services
  • >Appointments
  • >Tap Payments and payout workflows
  • >Earlier Stripe payment integration later migrated to Tap Payments
  • >AWS S3 and CloudFront media storage
  • >SMS, email, and push notification integrations
  • >Maps and location handling
  • >Reviews and disputes
  • >Discounts and business hours
  • >Reporting and business earnings workflows
  • >Admin verification and moderation workflows

Backend & API Architecture

-Reviewed backend contains 31 route definitions, 36 controllers, 34 repositories, 9 middleware modules, and 5 background-job files
-Prisma schema documents roughly 50 normalized tables and 55 enums in the PostgreSQL migration target
-API contract is documented with OpenAPI/Swagger and the repository includes 19 unit, integration, and end-to-end test files
-Current backend README identifies Redis, AWS S3/CloudFront, SNS/SES, Firebase Cloud Messaging, and Tap Payments integrations

08. Engineering Challenges

Keeping the booking flow responsive on mobile devices

Structured the screens and state transitions around the booking journey.

Handling payment and media workflows cleanly

Separated Tap Payments actions from AWS object-storage uploads.

[SYSTEM_SPECIFICATIONS]
ROLE:
Full-Stack Mobile Developer
CATEGORY:
Mobile
TECHNOLOGY STACK:
React NativeExpressTypeScriptPrismaPostgreSQLAWS S3Tap PaymentsREST APIs
BUSINESS IMPACT:
Provides a structured mobile booking foundation with a documented API contract and layered backend suitable for continued deployment work.