All work
Studio booking app and back officeIn development

Nedaa Lifestyle

An Arabic-first mobile app for a women-only Pilates studio in Nazareth: members book and cancel classes, and the trainer runs the studio from the same app, on top of the website's existing booking and payment data.

Member home on a phone: the studio photo, the next class, sessions left as dots and open classes this week
Built forA boutique fitness studio, its members and its trainer
My roleProduct design, mobile engineering and the WordPress integration
StatusPrivate client build; iOS on TestFlight, plugin live on the studio's site

Problem

The studio already ran on WordPress, Amelia bookings and PayPlus payments. A second system would have split members, packages and payments in two.

What shipped

Members: weekly schedule, booking and cancelling, packages and sessions left, Arabic-first with English.

Back office in the app: approvals, attendance, payments and refunds, schedule, reports, admins and account deletion.

A WordPress plugin exposes Amelia and WooCommerce data to the app, so the website stays the single source of truth.

System shape

Nedaa Lifestyle

  1. 01

    Member app

    Schedule, bookings, packages and profile, with the trainer's screens behind a role.

  2. 02

    Plugin API

    Authenticated endpoints that replay the website's own booking calls server-side.

  3. 03

    Studio systems

    Amelia keeps capacity, packages and emails; WooCommerce and PayPlus keep the money.

The source and customer data stay private. This view shows approved, anonymized system evidence.

Evidence

Plugin live on the studio's production siteBooking and cancelling tested against real classesAudit log for every admin action

Tools & interfaces

ExpoReact NativeTypeScriptWordPress plugin (PHP)AmeliaWooCommercePayPlusEAS

Next honest step

Walk the admin screens on a phone, test a real refund, then ship the iOS and Android builds.

Discuss a similar system