Mobile · iOS & Android · shared backend
From website to their clients' pockets in six weeks
Anonymized · representative engagement
A studio with a loyal following wanted what the big chains have: booking, class packs, and loyalty in an app. We designed and shipped iOS and Android apps on a shared backend with their existing site — one source of truth for schedules, one login for members, push reminders that actually get people to class.
6 wks
from concept to both app stores
38%
of bookings now happen in-app
2×
class-pack renewals with push nudges
1
shared backend with the website
The operations log
Week 1
Architecture that won't rot
Timberwright engineerOne backend serves the website and both apps — schedules, accounts, and payments defined once. No 'the app shows different classes than the site' ever.
Weeks 2-4
Built in the open
Timberwright engineerWeekly preview builds on the owner's own phone through TestFlight — feedback applied in days, not at the end.
Week 5
The details that make it feel premium
Timberwright engineerFace ID login, calendar sync, waitlist auto-promotion with instant push, and loyalty punch cards that fill themselves.
Week 6
Shipped to both stores
Timberwright engineerApp Store and Google Play, first submission accepted on both. Launch email and QR posters included.
Ongoing
Apps join the nightly watch
Autonomous agentCrash reports, store reviews, and backend health monitored nightly alongside the website — one care program for their whole digital presence.
✓ 4.9★ average across both stores
An app is a commitment, not a checkbox — it has to earn its home-screen spot every week. Built on a shared backend with nightly care, it stays worth it. Details anonymized; this engagement is representative of our product work.