One gym. Two connected experiences
Native apps for the people running a gym and the members training there, connected through a Node.js backend.
Gym teams needed to keep track of attendance, expiring memberships and outstanding balances. For members, the product had to make fitness content and daily routines easy to reach. These different tasks shaped the product’s structure.
Manager images are original onboarding screens supplied with the project. Member screens are cropped from the original interface design board. These are historical design assets, not captures from a running app; example dates and values are not adoption or fitness results.
Original onboarding screens introduce the gym’s administration tools. The Android implementation also includes a dedicated attendance list.
Open a member record, update its photograph and access contact or chat actions.
Choose a plan, enter a payment amount and method, and handle outstanding balances during renewal.
The member app’s home feed brings fitness posts and exercise videos together, with comments on individual posts.
The workout flow moves from exercise selection to choosing days, with a confirmation before copying a routine across the week.
Breakfast, snacks, lunch and dinner have their own entries, with a time field for the reminder.
Bring us your idea. We’ll shape the next step together.
What our clients value about working with Daphnis Labs.
The team at Daphnis Labs redefined what’s possible for Urbanface. They delivered a bespoke, animation-heavy website that remains incredibly quick and functional. The…
We wanted a unique, 'one-of-a-kind' feel for Glareen, and Daphnis Labs delivered an ecosystem that is both beautiful and technically superior. Their expertise in…
The level of technical depth Daphnis Labs brought to our Game project is unparalleled. While the front-end reel games are visually stunning and highly engaging, the…
Practical perspectives on AI, product engineering, commerce and modern software delivery.
Measure recovery by restoring into an isolated environment and checking the application, roles and dependencies that need the data.
Read Blog
Classify responses before caching them, make cache keys reflect their audience and test what happens when permissions change.
Read Blog
Review database roles, background jobs and exports together when designing row-level security for a shared application database.
Read Blog
Plan rollout, fallback behaviour and flag removal together so temporary release controls do not become permanent product complexity.
Read Blog
Connect traces, metrics and structured logs around a real failure path so the team can locate an incident and choose a next action.
Read Blog
Define permissions around concrete actions, and make an approval apply to the exact message or record that will be changed.
Read Blog
Separate parsing, validation and approval so an ordinary spreadsheet upload does not become an opaque bulk edit.
Read Blog
Give images, third-party scripts and interactions measurable limits, then investigate regressions by page template and device.
Read Blog
Help people complete a form with persistent labels, specific errors, preserved answers and a clear confirmation state.
Read Blog
Separate event receipt from order processing, record duplicate deliveries and recover work that stops halfway through.
Read Blog