Building SalonBook: a mobile booking platform with user and owner roles

Context: a booking workflow with two perspectives

SalonBook is a mobile booking-platform project built with React Native, Expo, and Firebase. The project was developed during 2024–2025 academic software-project work. It is presented here as an academic project, not as a client engagement or a claim about a live commercial product.

A booking workflow naturally involves more than one perspective. A person using the application needs a customer-facing path through the product, while an owner needs a view that reflects a different set of responsibilities. SalonBook was designed around separate user and owner roles so those two sides of the workflow could be considered as part of the same product rather than treated as a single generic account experience.

Team leadership in an academic project

Shahzaib Ahmad led a 4–5 member team for this academic software project. His contribution included planning, code review, milestone tracking, and end-to-end project delivery. This was team leadership within an academic setting, not a claim of sole authorship or solo ownership of the work.

The project process used Agile sprints, code reviews, and milestone tracking. These practices gave the team a shared way to organise work, review implementation, and follow the project through its planned stages. No productivity, speed, or delivery-outcome metric is claimed here; the point is to document the working process used by the team.

Mobile implementation and role separation

The application was built with React Native and Expo, with Firebase supporting the booking SaaS. React Native and Expo provided the mobile application foundation, while Firebase backed the application’s data and service needs. The case study focuses on the implementation choices recorded for the academic project rather than making claims about scale, performance, or public availability.

Separate user and owner roles were a central product consideration. Thinking through role separation helps a booking product distinguish the actions and information needed by a user from those needed by an owner. In SalonBook, that separation was part of the project’s stated design and implementation scope.

For the team, a mobile booking project also meant considering how role-specific screens and booking-related information belong together in one application. The approved project record does not publish client data, usage figures, booking totals, ratings, or commercial outcomes, so this case study keeps the discussion focused on the product structure and the technologies used.

Project presentation

SalonBook was presented at a university showcase and recognised by the Department Head for innovation. This is the project context recorded in Shahzaib’s resume. It is included as a description of that academic presentation and recognition, not as an award, certification, testimonial, institutional endorsement, or a measure of product performance.

The project remains a useful example of Shahzaib’s experience leading a small academic team through a mobile product build: defining role-aware product work, coordinating the team’s process, reviewing code, and taking the work through its project milestones.