Harmonia Pilates

Booking System & Mobile App

Harmonia Pilates is a premium studio offering reformer-based Pilates classes. We built a complete digital ecosystem including a responsive website and a mobile app for booking, class management, and user accounts.

View site A similar project?

pilatesharmonia.com

CASE STUDY

The context

Harmonia Pilates is a premium reformer Pilates studio based in Casablanca. The studio serves a regular clientele that books by session packs and values the ease of managing appointments from a phone. The project scope covered both the marketing site and a full booking ecosystem: a web interface for home bookings, an iOS and Android mobile app for clients on the go, and an admin panel for instructors. The promise to the studio: run everything from a single tool, with no third-party platform dependency.

The challenge

Three business logics coexist: single session, credit pack (10 sessions paid upfront), and monthly subscription. Each has its own cancellation rules (24h, 12h, free), pricing, and waitlist behaviour. Payments are validated manually by the studio (bank transfer, cash, card in store), so the system couldn't rely solely on automated Stripe capture. On the mobile side, the app had to ship on both stores while keeping a design consistent with the website, without rewriting the UI twice.

Our approach

Laravel backend for the business logic (session models, credits, instructors, time slots), exposed as an API consumed by both the React frontend (via Inertia.js, to keep a monolithic admin experience) and the mobile app. React Native for the app, which gave us a shared iOS/Android codebase and a mutualised design system with the website. The Filament-style admin panel lets instructors see today's schedule, mark attendance, and credit a cash payment. Push notifications via Firebase for session reminders.

The outcome

The ecosystem is live: responsive website, iOS app on the App Store, Android app on Google Play, operational admin panel. 70% of bookings come from the mobile app, which was the scoping hypothesis. The studio dropped the third-party SaaS tools it used before and now runs all booking, client, and payment operations from the delivered interface. On the technical side, the API-first architecture lets us add other surfaces (in-studio kiosk, partner page) without rebuilding the backend.