01
The member side, on their phone
The schedule, a tap to book, their upcoming classes, and a check-in that works at the door — plus their attendance history, which is the part that keeps them opening it.
Use case — native mobile app
Build the check-in app your members open at the door
Gym software is priced per member and still cannot express your class rules, your class pack, or the way Saturday works. Meanwhile check-in is a laminated sheet and attendance is a guess. What a studio needs is a member app that books a class and checks in, and a front-desk view that shows who is in the room — which has to be a real app, because a member is not going to bookmark a web page and open it at the door every morning.
- Real React Native and Expo — native navigation and native components, not a web view
- Push reminders for classes through expo-notifications
- Members, classes and attendance in your own Supabase project
- A front-desk view over the same data
- Scan a QR code and run it on your own phone through Expo Go while you build
- Cloud builds through EAS reach TestFlight and Play internal testing
Start with this prompt
Paste it in and edit the details to match your own. Being specific about the screens and the data is what separates a working app from a mockup.
Build a native mobile app for a climbing gym. Member side: a weekly class schedule with spaces left, a tap to book, and My Classes with upcoming and past. A Check In button that is only active within thirty minutes of a class I have booked. An attendance screen showing how many sessions I did this month. Staff side, behind a sign-in with a staff role: the next class, who is booked, who has checked in, and a manual check-in. Rules: classes have a capacity, booking is blocked when full, and cancelling within two hours is not allowed. Data in Supabase: members, classes, bookings and check-ins. Send a push reminder an hour before a booked class. Seed two weeks of classes and a few members.
What to build next
- Add a waitlist that promotes the first member when someone cancels.
- Add class packs: ten sessions, decremented on check-in.
- Add a monthly attendance summary for the owner.
Native mobile app
What the build actually consists of
For independent gyms, studios, climbing walls and clubs with a few hundred members and a process that does not fit the per-seat platforms. If you are running thousands of members with payroll and franchise reporting, that is a different purchase.
02
The desk side, on the same data
Who is booked into the next class, who has checked in, and a manual check-in for the member who forgot their phone. Same Supabase database, different screen, one sign-in with roles.
03
Reminders that bring them back
expo-notifications for a class reminder and a nudge after a week away — a real push notification, which is the whole reason this is a native app rather than a page.
What you get
- A class schedule members can book from, with capacity enforced
- Check-in at the door, and a manual check-in at the desk
- Attendance history per member
- Class reminders as real push notifications
- A staff view of who is booked and who has arrived
Describe it. Watch it build.
Paste the prompt above and scan the QR code when the build lands — the app runs on your own phone while you are still changing it. The free plan needs no card.
Start buildingFAQ
Questions, answered.
Can members pay for memberships in the app?+
For a subscription sold inside an iOS or Android app, Apple and Google require their own in-app purchase — RevenueCat is one of our nine connectors and is the usual way to do that. Stripe, also a shipped connector, is the right tool when the membership is sold on the web instead. Which one you want depends on where the sale happens, and it is worth deciding before the first build.
Does check-in need a QR code or a scanner?+
Not necessarily — a time-windowed check-in button covers most studios. If you want a scanned code at the door, expo-camera can read one; say so in the prompt and it will be built that way.
Can staff use it without installing an app?+
Yes. Build the desk view as a web app in the same account over the same Supabase database. Vibely builds both, so the two never drift apart.