Platforms & SaaS
Beauty marketplace case study: web and mobile applications sharing an API for salon discovery, booking, packages and product commerce.
Project overview
IM Beauty Glow is a consumer-facing beauty and salon marketplace built as a matched pair: a Next.js storefront and a React Native companion app sharing the exact same backend API contract, down to the request field names. Guests discover salons, book individual services or bundled packages and offers, shop salon products, and manage their bookings and orders from either surface interchangeably. Salons list themselves and manage their presence through the same platform.
The challenge
Guests expect to research, book, and pay for a salon visit from whichever device is in front of them, and a mobile booking flow that quietly disagrees with the website's pricing or availability rules erodes trust immediately. The product also had to sell three different things — individual services, discounted packages, and time-boxed offers — through one booking flow without turning it into three separate systems.
Technical approach
The web app owns the commerce surface end to end — salon discovery, services, packages and offers, cart, checkout, payments, and account management — behind a typed API layer that keeps booking, cart, tax, and payment logic out of the presentation layer. The mobile app was built to mirror that contract exactly rather than re-implement it: before extending the app to book offers and packages, I verified the live web and backend validation rules first, then extended the existing appointment flow to accept three booking sources — service, offer, or package — through the same endpoint and the same optional identifiers the web app already sent. Package and offer pricing stays server-authoritative rather than recalculated on-device, so a discount can never drift between the two apps.
Salon self-onboarding
The "List Your Salon" flow salons use to self-onboard: owner details, business profile, location, services, and hours in one guided multi-step form.
Salon detail
A salon detail page: service catalog with pricing, top specialists, and a direct booking action, the same view a guest uses on web or in the companion app.
Products and interfaces
Platform breadth
Evidence
Facing a similar problem?
For founders about to build or rebuild a web, mobile or SaaS product.
Request an assessmentExplore the approach
Questions and answers
More questions? Feel free to reach out.
Discuss a related project →IM Beauty Glow is a consumer-facing beauty and salon marketplace built as a matched pair: a Next.js storefront and a React Native companion app sharing the exact same backend API contract, down to the request field names. Guests discover salons, book individual services or bundled packages and offers, shop salon products, and manage their bookings and orders from either surface interchangeably. Salons list themselves and manage their presence through the same platform.
The work includes Consumer web storefront (salon discovery, booking, cart, checkout, account), Companion iOS/Android app (React Native), Salon self-onboarding flow ("List Your Salon"), Shared booking flow for services, packages, and offers, SEO pipeline (sitemap and .htaccess generated at build), Push notification integration (OneSignal, Notifee).
Muhammad Muzammil Qureshi served as Chief Technology Officer, with responsibility spanning technology direction, architecture, delivery, and the operating systems described in this case study.
IM Beauty Glow uses Next.js 15 · React 19 · TypeScript · Tailwind CSS v4 · React Native 0.86.
The Next.js web app owns the commerce surface — discovery, services, packages and offers, cart, checkout, and account — behind a typed API layer that keeps booking, cart, tax, and payment logic out of the presentation layer. The React Native companion app mirrors that contract exactly, and package and offer pricing stays server-authoritative rather than recalculated on-device, so a discount can never drift between the two apps.
Yes. The same booking flow accepts three sources — an individual service, a discounted package, or a time-boxed offer — through one endpoint and the same optional identifiers the web app already sends, so packages and offers were added without building a separate booking system.
Salons self-onboard through the "List Your Salon" flow, submitting their business details, location, services, and hours. Once listed, they manage their public profile, bookings, and product commerce through the same platform guests use.
The web storefront spans 47 routed pages and the companion mobile app 29 screens, both built to one identical backend contract down to the request field names. The mobile codebase was verified with zero TypeScript and zero ESLint errors after a dead-code and mock-data removal pass.
Let's build what's next
Whether you are starting from an idea, replacing an existing platform, or scaling a system, let's talk.
Better Technology.
Brighter Possibilities.
