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.
Separate Kimi's API and coding-plan limits, budget cache writes correctly, and evaluate a repository refactor against behavior that must survive the change.
Read Blog
Budget beyond Mercury 3's launch discount, check its streaming and reasoning defaults, and measure how quickly a support agent produces a correct, usable answer.
Read Blog
Separate the model's context from each provider's limits, calculate a coding-pilot budget, and test a mobile layout repair before committing to self-hosted hardware.
Read BlogCompare recorded and realtime transcription costs, identify launch-documentation conflicts, and test whether a corrected collection request survives the trip from audio to an operations draft.
Read Blog
Check the released model's token rates and API compatibility, calculate a realistic pilot budget, and evaluate image evidence against changing inventory records.
Read BlogSeparate GLM-Legal's beta access from unconfirmed API terms, interpret its independent benchmark results, and test document evidence with a reviewer-inclusive cost model.
Read BlogCheck the October 17 model update, peak and off-peak token rates, and new search charges, then evaluate an agent against versioned API evidence.
Read Blog
Understand Timestral's time-step limits and weight license, estimate a local forecasting job, and design a retail backtest that cannot see future sales.
Read BlogCheck Sonnet 5.5's token costs, thinking settings and conversation requirements, then evaluate coding changes against a concrete merchant-sorting fixture.
Read BlogCheck Gemini 4 Argon's access rules, shared token budget and launch pricing, then use a controlled supplier-data evaluation to plan an API migration.
Read Blog