HairZone
React Native barber-booking application backed by a modular Express and TypeScript API for customer, business, appointment, payment, media, and administrative workflows.
01. Overview
React Native barber-booking application backed by a modular Express and TypeScript API for customer, business, appointment, payment, media, and administrative workflows.
02. Interface / Screenshots

03. Architecture
Interactive Architecture Walkthrough — a visualization of the implemented architecture/workflow.
Interactive Architecture Walkthrough
A React Native booking flow covering customer profiles, services, appointments, payments, notifications, maps, and administration. [Visualization of the implemented mobile workflow.]
04. Problem
Local barber businesses need a clearer way to manage bookings, profiles, payments, and operational visibility on mobile.
05. 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.
Backend focus
- -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
06. 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
07. Engineering Challenges
Structured the screens and state transitions around the booking journey.
Separated Tap Payments actions from AWS object-storage uploads.
08. Outcome
Provides a structured mobile booking foundation with a documented API contract and layered backend suitable for continued deployment work.