Selected work FITNESS & WELLNESS / PRODUCT ENGINEERINGCASE STUDY 01

Tiger Fitness · Web + mobile

One gym.One connectedexperience.

From the front desk to the final rep.
A shared platform for the people running the gym
and the members making progress.

Explore the story
THE PLATFORM IN FOCUS01 / TEAM & MEMBER EXPERIENCES
Built to work together.Web operations × member mobile

Web: existing desktop demo capture. Mobile: reconstructed reference screens with sample data. Click a screen to explore.

THE PRODUCTTiger Fitness
THE EXPERIENCESStaff web · Member web & mobile
THE SCOPEOperations · Coaching · Self-service
THE FOUNDATIONReact · Flutter · .NET · SQL Server

A better gym experience
starts behind the scenes.

Memberships, payments, attendance, coaching, retail and maintenance all shape the member experience. The product challenge was to connect those workflows without making every person navigate the same interface.

The team gets a web workspace built around daily operations. Members get their own web portal and a Flutter companion built around today’s next step. A shared API joins the experiences.

02↗

Primary client experiences
React web & Flutter mobile

01↗

Shared backend foundation
Identity, services & operational data

05↗

Focused member tabs
Home, Workouts, Diet, Progress, Profile

01

Make the next action clear.

Give reception and owners a useful route through onboarding, payment collection, upcoming renewals and daily work.

02

Close the coaching loop.

Connect coach-authored plans to member assignments, workout execution and recorded activity for review.

03

Bring the member along.

Keep plans, membership standing and progress close at hand, through focused self-service on web and mobile.

The whole operation.
A clearer view.

A React workspace for owners, reception, trainers and accounts staff. Role-aware access keeps workflows relevant; shared member profiles connect the work.

A shared program library supports workout planning, assignments and training review.

DESKTOP DEMO CAPTURE · CLICK TO ENLARGE

Onboarding that continues.

Create a member, validate a CSV import, assign membership and payment, then continue through coach, workout and diet setup from a shared profile.

MembersCSV previewOnboarding checklist

Billing with a next step.

Membership standing separates access eligibility, plan period and outstanding balance. Collections, installments, receipts and renewals have distinct workflows.

Membership standingReceiptsRazorpay integration

Daily work, in focus.

Dashboards and work lists surface renewals, balances, lead follow-ups and operational exceptions alongside attendance and business summaries.

Daily workQR accessOwner reporting
ALSO CONNECTED

Personal training · Diet assignments · Retail POS · Inventory · Expenses · Cleaning · Lockers · Notifications

The gym experience.
In your pocket.

The Flutter member app puts check-in, today’s assigned workout and membership standing within reach. Its PulseFit / Tiger Fitness experience uses the same backend as the web app.

Six reference views. One member journey.

01 / TODAYOne useful next step.

Check in, start or resume a workout, and understand membership standing.

02 / WORKOUTSFrom plan to practice.

Coach-assigned sessions, warmups, live set tracking and workout summaries.

03 / NUTRITIONGuidance you can follow.

Assigned meals and macro targets, with daily water entries stored on-device.

04 / PROGRESSRecords that tell a story.

Weigh-ins, recorded check-ins, completed workouts and transformation photos.

05 / MEMBERSHIPKnow where you stand.

View access and billing status, receipts and online checkout when enabled.

06 / PROFILEYour account. Your control.

Profile, health assessment, assigned supplements, devices and support.

Mobile references are reconstructed illustrations based on the Flutter app’s implemented flows and design tokens, with sample data. They are not authenticated device screenshots.

Ready for interruptions.

Cached member information and offline workout recovery help a session continue. QR check-in and payment require connectivity.

Personal, by design.

Member-scoped services expose the signed-in member’s plans and records. Assigned targets remain distinct from logged activity.

Clear about payments.

Native Razorpay checkout can settle a balance when configured. Renewal remains a separate front-desk workflow.

Every handoff.
One shared story.

The member reception creates is the same person the coach assigns a plan to, the app checks in and the platform records progress for. Each step builds on the previous one.

01

Onboard.

Create the profile, assign a membership and follow the checklist through billing and coaching.

RECEPTION / WEB
02

Assign.

The coach builds and assigns workout and diet plans to eligible members.

COACH / WEB
03

Check in.

Scan the branch QR. The API checks eligibility and records the visit.

MEMBER / MOBILE + API
04

Train.

Follow an assigned session, track the workout and record body metrics over time.

MEMBER / MOBILE + WEB
05

Review.

Recorded activity supports coach review; membership standing clarifies what comes next.

CONNECTED WORKFLOWS

Two clients.
One source of truth.

The web and mobile interfaces are purpose-built for different people. Shared identity, business rules and operational data keep the underlying product connected.

TEAM & MEMBER WEBReact + TypeScriptVite · TanStack Query
MEMBER MOBILEFlutterFocused member workflows
AUTHENTICATED SHARED APIASP.NET Core 9Permissions · Memberships · Billing
Training · Attendance · Member records
OPERATIONAL DATASQL ServerEntity Framework Core
Shared identity & history
01 / IDENTITY

One person, connected roles.

Shared identity links member, trainer and staff profiles. Role and permission checks govern access; member endpoints scope records to the authenticated person.

02 / PERFORMANCE

Request what matters.

Server-side paging, summary APIs, caching and compressed responses reduce dependence on full-table downloads and repetitive dashboard requests.

03 / RELEASES

A staged path to release.

Separate UAT and production environments support review before promotion. The repository includes .NET, web and Flutter checks alongside release workflows.

Connected work.
Better possibilities.

The result is a connected product foundation: operational oversight for the team, a route from coaching to execution, and self-service for members across channels.

A defined front-desk journey.

Onboarding, membership standing, payment collection and renewal review each have an explicit next action.

Self-service beyond reception.

Members can access assigned plans, billing details and recorded progress through their own web and mobile experiences.

Coaching connected to training.

Program planning and assignment connect to live member sessions and recorded activity for ongoing review.

A product that can be extended.

Shared services and identity let future development build on existing workflows instead of duplicating the foundations.

These outcomes describe implemented capabilities. Revenue growth, retention uplift, time savings and performance gains have not been independently measured for this case study. Screen values are demo or illustrative data, not business results.

THE DETAILS MATTER

Useful answers.
No guesswork.

How are the web and mobile apps connected?

Both clients use the shared ASP.NET Core API. Staff and coaches manage gym workflows on the web, while members access their own plans, membership and recorded activity through scoped services.

Can members pay online?

The implementation supports Razorpay on the member web portal and native checkout in the mobile app when the gym enables and configures it. Settling a balance does not purchase a new membership period; renewal is separate.

What happens if connectivity drops?

The mobile app caches selected previously loaded information and supports offline workout recovery and synchronization. QR attendance and online checkout require connectivity.

Does nutrition include a food diary?

The app displays coach-assigned meals and planned macro targets. Food search filters the assigned plan; daily water entries are stored locally. Planned targets are not presented as consumed food or measured adherence.

Are these screenshots of the live app?

The web gallery uses existing desktop demo captures from this project. The mobile gallery uses reconstructed reference illustrations based on implemented Flutter flows, with sample data. These references do not imply an app-store release or live payment availability.

LET’S BUILD WHAT’S NEXT

Your ambition.
Our next great build.

A web and mobile product built around your business,
your team and the people you serve.

Discuss your project

Product screen

Web captures use demo data. Mobile screens are reconstructed illustrations. Escape closes the preview.