Case study

One app to find, book and play.

Sportyfia wanted to bring turf and gym booking out of phone calls and WhatsApp groups. We designed and built Phase 1: a Flutter app for iOS and Android where players book venues and gyms, owners manage their slots, and the Sportyfia team runs everything from a web admin panel.

Visit live site ↗Start a similar project

Client: Sportyfia
Industry: Sports · Marketplace
Services: UX/UI design, Mobile app development, Backend & APIs, Admin panel, Store launch
Platforms: iOS, Android, Web admin
Live: www.sportyfia.in ↗

app for players and venue owners: 1
feature modules in the mobile app: 10
admin panel sections: 15
gym membership plans, day pass to annual: 8

The challenge

Booking a turf in most Indian cities still means calling the owner, asking what's free and paying in cash when you arrive. Owners juggle slots in notebooks and chat threads, and players can't compare venues at all.

No live availability
Players couldn't see open slots without calling around, and double bookings were common.
Owners without tools
Venue and gym owners had no simple way to publish availability, block time or see what they'd earned.
Cash and no-shows
Without upfront payment, no-shows cost owners real money and cancellations had no clear rules.
Two businesses in one
Turfs sell time slots and gyms sell passes and memberships. The product had to handle both without feeling like two apps.

Our approach

We scoped a focused Phase 1 that makes booking reliable, then built the foundation so tournaments, match hosting and more can plug in later.

01
One app, role-based
Every user is a player. Once an admin approves their venue or gym submission, the same account unlocks host tools, with no second app to install.
02
Continuous slots only
Multi-slot bookings must be back to back. That one rule removes a whole class of scheduling edge cases for owners.
03
Pay upfront, with fair rules
Razorpay checkout with webhook verification, plus a clear cancellation window, protects owners without punishing players.
04
Rewards that drive repeat play
Points on every booking unlock coupons at a threshold, which keeps players coming back without complex loyalty tiers.

What we built

Three connected surfaces: the player app, host tools inside that same app, and a web admin panel.

Players

Phone OTP and Google sign-in
Search venues and gyms, filter by price, distance and sport
Venue pages with photos, rules, amenities and reviews
Multi-slot booking, coupons and Razorpay checkout
Gym day passes and 8 membership plans
Booking IDs, sharing, reviews and reward points

Venue & gym owners

Submit a venue or gym for approval
Manage details, operating hours and availability
Block slots for walk-ins or maintenance
See bookings as they come in
Basic earnings summary

Sportyfia team

Users, venues, gyms and memberships
Venue and gym approval and rejection
Booking oversight and revenue view
Coupon, reward and banner configuration
Review moderation and support desk
Push notification campaigns

Architecture and stack

A typed backend with clean module boundaries, so Phase 2 features slot in rather than bolt on.

Mobile

Flutter
Riverpod
go_router
Dio
Hive
flutter_map

Admin

Next.js
TypeScript
Radix UI
Tailwind CSS

API

Node.js
Express
TypeScript
JWT + role-based access
Admin 2FA

Data & services

MongoDB
AWS S3
Razorpay + webhooks
Twilio OTP
Firebase Cloud Messaging

The details

Checkout

Pricing the platform can explain

Every checkout runs through one pricing service that splits the amount into the host's share, the platform commission, a convenience fee and GST on that fee. Gyms get tiered commission by plan length, overridable per gym. Because every booking stores its own breakdown, payouts and refunds stay auditable.

01One source of truth for every rupee in a booking
02Per-gym commission overrides by membership tier
03Platform-funded discounts capped by platform revenue
04Host payout calculated at booking time

Cancellations

A cancellation policy written as code

Cancellations follow a published policy in venue-local time: a cutoff window, a user fee and a defined split that compensates the host for a lost slot. Refunds, reward reversals and host settlements are tracked as separate states, and a background job retries anything that fails.

01Time-zone-aware cutoff (Asia/Kolkata)
02Separate refund, reversal and settlement statuses
03Rewards reversed automatically on cancellation
04Retry job for failed benefit reversals

Engagement

Rewards, coupons and campaigns

Points are posted as ledger transactions on each successful booking, coupons activate at a threshold, and redemptions deduct points atomically. The admin team can configure all of it, and send targeted push campaigns through Firebase Cloud Messaging.

01Ledger-style reward transactions
02Coupon configs, per-user usage and redemptions
03Scheduled campaign sender job
04In-app and push notifications

How it came together

Step 01
Scope & design
Turned a broad vision into a signed Phase 1 scope, then finalised designs for every player, host and admin screen.
Step 02
Auth & onboarding
OTP and Google sign-in, role-based access, admin 2FA and the venue/gym submission and approval flow.
Step 03
Venues & gyms
Discovery, slot and plan management, and booking flows for both sides, built and demoed module by module.
Step 04
Payments & launch
Razorpay with webhook verification, rewards, the admin panel, then production deployment and store submission.

The outcome

Phase 1 gives Sportyfia a production platform for iOS, Android and the web, with the operational tools to run it and a foundation for tournaments and match hosting next.

Booking without the back-and-forth
Players see real availability and pay upfront, and owners stop managing slots over the phone.
An operator's cockpit
The Sportyfia team approves venues, moderates reviews, runs promotions and sees revenue in one place.
Built for Phase 2
Tournaments, match hosting and wallets were scoped out deliberately, and the architecture already has room for them.