- 5 days ago
- 7 min read
How Samprand, a Miami-based web agency, built a full-featured Flutter fitness app with membership, video library, social feed, and more, entirely on Wix Headless.
The project started as a simple membership platform for a fitness creator with 2,000 Instagram followers. It ended up on the App Store. Here's how they built it, what they ran into and why they'd do it the same way again.
TL;DR
When fitness creator Tay came to Samprand with 2,000 Instagram followers and a dream of a membership app, the Miami agency turned to what is Wix Headless to make it happen.
What followed was a full Flutter fitness app: membership management, video library, social feed, fitness tracking, threaded comments and more, built entirely on the Wix backend and now live on the Apple App Store and Google Play. Tay now has 40,000 followers and runs her entire content operation herself, without a single dev dependency.
"We don't have to stray too far from Wix in order to add this functionality. A lot of the things we needed were right there in the API." — Jonathan Cantillo, Samprand
Learn more: what is Wix Headless?
A client with ambitions and a team with motivation
When Namastay with Tay first came to Samprand, she had about 2,000 Instagram followers and a simple ask: build a membership platform for her fitness video content.
No app yet, no custom platform, just a way to monetise her audience beyond Instagram Live, a proper membership website builder that could grow with her.
Samprand started where any agency would: finding the client the best solution, both for the build and for the client to manage day-to-day. They already had many Wix projects in their portfolio. But would Wix be able to scale this business and open new horizons for Tay?
The answer was yes.
Thanks to the minimal setup requirements of Wix Headless and the built-in CMS for all of her structured content, Tay's Namastay Sweaty Club app started to take shape. And what followed was a steady accumulation of features until Tay's dream came true and her app appeared live on the Apple App Store and Google Play.
API challenges, CMS solutions
"We realized we could recreate that same functionality with the media manager plus the CMS."
Tay's video library was growing steadily, with many of her workouts already uploaded to Wix. It made sense for Samprand to build on top of what she already had. But they hit a snag when looking for specific endpoints for these videos: the Wix SDK offered a lot of functionality, but the endpoints they needed for video (titles, descriptions and other content) weren't yet exposed.
Instead of looking for another path, the Samprand team got creative and took full advantage of the Wix CMS and Media Manager to replicate everything Wix Video couldn't expose. It didn't just work. It worked incredibly well.
Once the team expanded the app's video capabilities with the CMS, the floodgates of product creativity opened. Many other limitations were lifted the same way. Groups, community, comments, fitness tracking and favorites, all of this functionality was custom-built by Samprand in the Wix CMS, and Tay's app was growing fast.
"That's a testament to how well the CMS works."
A performance-first stack: Flutter + Wix Headless
The full architecture is as simple as it is powerful, and it delivers on performance. The entire backend lives on Wix. The frontend is Flutter, chosen for its speed, its cross-platform reach, and the snappiness of the user experience it delivers.
"I'm hitting the random button and it is bringing a random class every single time, essentially immediately. So no lag there."
What lives on Wix:
All video content, hosted on the Wix Media Manager.
The full CMS: video library, categories, user tracking data, comments, favorites and community posts.
Authentication and membership management, fully Wix-managed.
Wix Automations for user engagement, segmentation and retention flows, managed by the client alongside the agency.
Marketing pages and the public-facing site.
What lives on Flutter:
The Flutter app (iOS and Android), consuming Wix APIs in real time.
Flutter Web for the authenticated portion of the website, using the same codebase.
The AI layer:
GitHub Copilot and OpenAI Codex accelerating development and feature implementation.
The Wix MCP used for responsive testing and UI debugging across screen sizes.
The Namastay Sweaty Club Stack:
Layer | Tool |
Mobile App | Flutter (iOS + Android) |
Web Platform | Flutter Web |
Video & Media | Wix Media Manager |
All Content & Data | Wix CMS |
Auth & Memberships | Wix-managed |
Automations | Wix Automations |
Payments | Wix + Stripe |
AI Dev Tools | Wix MCP, GitHub CoPilot, Codex |
Client Dashboard | Wix Business Manager |
This stack serves a high-performance native app and a web platform simultaneously. The result is a single, unified backend that the client manages herself without developer involvement for day-to-day content, and a lot of satisfied yogis, thanks to Tay's classes.
Learn more: what is the Wix MCP?
An ever-evolving user journey
Starting from a simple membership platform, the feature set grew with each client request, and each one was solved inside the same Wix CMS architecture. This short breakdown gives an idea of how Samprand leverages Wix's Business Manager and CMS to deliver a refined user experience:
Video library with fitness tracking. Every class a user watches can be tracked with a tap. The action writes to the CMS in real time: user ID, class ID, timestamp. Five completions of the same class trigger a celebration animation. The calendar view pulls from that same CMS table and renders the user's history by date, live, with no caching.
Commenting system. The team built a threaded comment system from scratch on the CMS. Main comments, replies, and nested replies, all written and read from Wix in real time while Tay can monitor it all.
Community feed. A full social posting platform, also CMS-backed, designed to mirror the feel and functionality of similar groups apps.
Stripe + Wix membership. When the client needed multi-currency support (Canadian and US dollars), they integrated Stripe for payment processing, while keeping all membership logic inside Wix. A member still has to exist in Wix even if they paid through Stripe, and the API handles activation automatically.
"She's probably the best client we've seen at implementing Wix Automations. You're not escaping this platform once you sign up."
Related readings:
The growth that followed, and the plan ahead
"When we started working with her, she had about 2,000 followers... and now she has 40,000."
Taylor started with an Instagram community of 2,000 followers and a modest, yet steady income from her classes. She now has 40,000 followers and she manages her entire content operation herself, uploading videos, managing categories and updating the CMS without developer support.
"We taught her how to use the CMS. And I think that's one of the biggest benefits of Wix. You don't have to be super tech-savvy to understand how to upload things to the CMS or change categories."
Samprand continues to work with Tay as her business expands and as she comes up with new feature ideas for her community. With the robust backend now established, trusted and running smoothly, Tay can think ahead with the Samprand team about which frontend frontiers she wants to conquer next. Smartwatches, fitness trackers, expanded features in the app and on the web, the sky's the limit.
Next steps for Samprand: Wix-first, AI-first, client-focused
"We want to bring all these AI capabilities to the small and mid-market. That's our mission as a company."
Samprand's approach is to stay in the Wix ecosystem wherever possible. If a client already has something on Wix, they find a way to keep it there.
Wix Headless is what makes that possible for projects that need code-level control: custom UI, native apps, complex data logic, without forcing the client to learn a new platform from scratch.
Wix Headless is the only headless solution that natively combines a CMS, eCommerce platform, payments, online scheduling and events in one place. No stitching, no third-party integrations, no separate vendors.
With the Wix MCP, Wix Skills and the SDK, the Samprand team is ready to bring Wix Headless to new and existing projects, focusing on the functionality they dream of building for their users, not the repetitive work of implementing auth, site security and basic logic over and over again.
Explore more Wix Headless user stories:
Build like Samprand
Paste wix-headless.dev/skill.md into Claude Code, Cursor or any AI tool you already use, and your project is connected to the full Wix backend instantly, no servers, no backend engineering, no slowing down.
Frequently asked questions about Wix Headless
What is Wix Headless?
Wix Headless is the only headless solution that natively combines a CMS, eCommerce, payments, bookings and events in one place. You build your frontend on any AI coding tool or code stack, connect it to the full Wix business backend in one prompt and manage everything from a single Wix Business Manager dashboard. No servers to run, no backend to engineer.
Can Wix Headless power a native mobile app?
Yes. Wix Headless supports any frontend technology or mobile stack that can call Wix APIs, including Flutter for iOS and Android. The Wix backend handles authentication, membership management, content, media and automations while the mobile frontend consumes Wix APIs in real time. The same backend can simultaneously power a native app and a web platform from one dashboard.
How does the Wix CMS work for custom app development?
The Wix CMS organizes content into collections that connect directly to any frontend UI through the Wix APIs. For custom app development, it provides structured, queryable data out of the box: video libraries, user tracking, comments, community feeds and more, all manageable from the Wix Business Manager without developer involvement. Clients can add, edit and reorder content without touching code.
How does Wix Headless support client handoffs?
Wix Headless provides clients a clean Wix Business Manager dashboard to manage their own CMS, blog and business tools independently, without needing developer access. Agencies can scope exactly what each client can edit, so clients stay self-sufficient and dev time stays focused on new builds. No plugins to manage, no servers to patch, no being the permanent help desk.
