Memberships, attendance and the everyday work of running a gym.
Gym teams need to connect member records, renewals, attendance and payments without losing the context of an individual membership.
The workspace includes dedicated web and mobile applications alongside the backend. Owners and members have different tasks, so each experience can focus on the work relevant to that role.
Separate applications require consistent API contracts and coordinated releases.
The migration history includes audit logs, bill voiding and subscription references that survive deletion. This supports reviewing what happened after a membership changes.
Historical records need explicit rules for correction and retention.
The schema includes date-system preferences and attendance timestamp indexes. Local presentation and efficient attendance lookup are represented in the data model.
Date conversion must stay consistent across reports and interfaces.
A connected set of owner, member and mobile applications, with explicit membership, attendance and billing records.
FastAPI · Web application · Expo mobile
Based on the project implementation and documentation. Tradeoffs explain the implications of these choices; no measured business results or client feedback are claimed.
Ready to turn your vision into production-grade software? Let's start the conversation.
Start Your Project