All work
Case Study — VASA Fitness Mobile App  ·  6 min read
Consumer Mobile Fitness

Better Than Starbucks

How a 10-person team built a native gym app that hit 300k installs and outshipped what Starbucks built with 70.

300k
App installs within three months of launch
$150k
In direct app revenue post-launch
4.3★
App Store rating across nearly 7,000 reviews
<6mo
From kickoff to both app stores
Client VASA Fitness, a national gym chain
Agency Neudesic
Role UX Designer → UX Lead
Timeline 2019 – 2021 · 13 months
Platform iOS · Android Native
Led UX across iOS and Android, design-development collaboration, stakeholder presentations, usability testing cadence, feature prioritization
Team 10-person cross-functional consulting team (designers, iOS and Android devs, PM)
Netpulse existing white-label app

A white-labeled app nobody liked

VASA Fitness, a national gym chain, had a real-app problem. Their existing white-label app was a Netpulse template shared across dozens of gym brands. All of VASA's actual member data, accounts, class schedules, payments, KidCare reservations, lived in a separate system called PAC. The two systems didn't talk to each other.

The result was maddening. Members logged into the app, got launched into a browser window, and had to log in again to a different system just to see their class schedule. Two logins, two interfaces, no continuity. KidCare scheduling, the daily-driver feature for the parents who made up most of the morning class population, wasn't available digitally at all. Members called the front desk to book it.

From designer to UX Lead

What I owned
  • UX lead across iOS and Android for a 10-person cross-functional team
  • Product direction and roadmap, replacing an underperforming white-label app
  • Decision-making frameworks (card sorts, priority matrices) to align team and client
  • Design-development collaboration: side-by-side reviews, junior dev mentorship
  • Direct presentation to VASA C-suite and stakeholder leadership
  • Two-round usability testing cadence at gym locations (guerrilla testing with 6 to 12 members, re-validation after iteration)
What I partnered on
  • VASA Chief Brand Officer Mindi Bridges on visual direction and brand extension
  • VP of Strategy Mehul Chaudhari on feature prioritization and Phase 2 planning

Eight thousand members, one mom

We surveyed over 8,000 VASA members before designing a single screen. The scale of that response was unusual for a project like this and gave us a dataset that was hard to argue with when it came time to make priority calls.

18mo
Average member dropout, retention was the core business problem
70%
Of members on iOS, informed platform priority and design investment
#1
Member frustration: no account access or management in the app

Three findings shaped the whole product. The average member dropped out after 18 months: retention was the core business problem. 70% of members were on iOS: that informed platform priority and design investment. The single loudest frustration across thousands of responses: members couldn't access or manage their own accounts through the app.

The reframe came from grounding everything in one user. A single mom in her early thirties who drops her two kids at KidCare before her morning class. She couldn't book KidCare digitally at all, and she couldn't see her own classes without logging into PAC separately. We wanted her to open the app on Sunday night, schedule her week's KidCare and classes in two minutes, and move on. That was the bar we designed toward.

Throughout the project, I ran guerrilla usability testing sessions at VASA gym locations, walking up to real members with prototypes on a phone, watching them try to complete tasks, and listening to where the design broke down. The first round surfaced filter pattern problems in both class scheduling and KidCare booking, plus friction in the membership purchase flow. After making changes, I went back to the gyms and put the revised prototypes in front of members again. The friction points were gone. That second round gave us the conviction to lock the designs and move into development.

Locking the visual direction with the C-suite

I worked directly with VASA's Chief Brand and Marketing Officer, Mindi Bridges, through rounds of moodboards, style tiles, and early concept designs to lock the visual direction before building a single production screen. That early investment paid dividends: when design questions came up later, we had a shared vocabulary vetted at the top, which meant I could move fast and make visual decisions with confidence rather than looping back for approval on every screen.

"Not only was Neudesic involved on the technical side, but they also became a strategic advisor on new features that we were looking to implement. Neudesic understood how we operate our business on a day-to-day basis and helped make recommendations. This took a lot of pressure off of our team, because we trusted that Neudesic had our best interests in mind."

Mindi Bridges, Chief Brand and Marketing Officer, VASA Fitness

Teaching Developers to See

About two-thirds of the dev team were junior engineers learning native iOS or Android for the first time. Rather than treat them as downstream executors, we pulled them in early into workshops, whiteboard sessions, the messy front end where decisions were still being made.

Once builds came back, I started doing side-by-side reviews. I'd sit with a developer, pull up the build on a device next to the design in Figma, and walk through it together, talking through intent. Why this spacing exists. What the user is trying to accomplish on this screen. It wasn't just QA, it was teaching them to read designs the way a designer reads them. At peak velocity, the 1:5 designer-to-developer ratio meant 50 to 70% of each working day in these reviews. The single most important thing I did for product quality.

By Phase 2, the gap between design intent and built output had narrowed significantly. Not because designs got simpler, but because the team had internalized how to read them.

The platform tradeoff

What shipped in Phase 1: barcode check-in, class and KidCare scheduling, membership purchase flow, gym locations, homescreen, real account access. Members could finally see their own membership information inside the app that bore their gym's name.

The platform tradeoff was the call that taught me the most. As the deadline closed in, it became clear we couldn't deliver the same quality on both platforms. iOS was strong. Android was functional but carried compromises. With 70% of VASA's members on iOS, we delivered a high-quality experience to the majority while replacing something broken for everyone else. We treated Android as a gap to close, not a permanent state.

Designing inside someone else's system

Every feature had to work within the API boundaries of PAC, a third-party platform built to manage gym operations from the back office, not power a modern mobile app. KidCare was the test case. No system supported it digitally; members had been calling the front desk. We worked with PAC to figure out what data was available, what scheduling logic could be built on top of it, and how to present it as something that felt native. From the member's perspective, it just worked. She had no idea what was happening underneath.

Deciding What to Build Next

After launch, the feature backlog exploded. I facilitated a card sort with VP of Strategy Mehul Chaudhari to force prioritization. Laid out every candidate feature, mapped them against member impact and technical feasibility, sorted them into a sequenced roadmap. It turned a sprawling wishlist into a focused plan the entire team could align around.

My job wasn't just to design the features. It was to help the client decide which features deserved to exist at all.

From designer to decision-maker

The principal designer moved on six months in. By then I was already running design-dev collaboration, presenting to VASA's leadership, and making product-level calls. The transition to UX Lead formalized a role I'd been growing into since the first sprint.

I became one of the primary communicators between VASA leadership and the delivery team. Translating business goals into design direction in stakeholder meetings, then translating design intent into implementation specifics in developer reviews. Two different audiences, two different languages, same product vision.

Three months. Three hundred thousand installs.

Phase 1 launched in November 2019, in time for the Thanksgiving marketing push. Less than six months from kickoff to both app stores. The numbers came in fast: 300k installs within three months, $150k flowing directly through the app, 4.3-star rating across nearly 7,000 reviews (still holds today).

Shortly after launch, a message from Mehul Chaudhari made its way to our team: VASA's CEO, CMO, and CFO were using the app to book classes and called it awesome. They noted that Starbucks had 70 developers on their app and couldn't release it in the same timeframe or for the same cost.

"Just got a call from our CEO/CMO/CFO who are using the app today to book classes and got feedback from the club. They said it was awesome and were super happy with it. They made an app at Starbucks with 70 developers and a bunch of other folks and couldn't release it in the same timeframe or for the same cost."

Mehul Chaudhari, VP of Strategy and Analysis, VASA Fitness

The trust built during Phase 1 led VASA to bring Neudesic back for two additional projects during the COVID recovery period in mid-2020, when every budget line was being scrutinized: a tablet sales tool and a self-service support site. Phases 2 and 3 of the mobile app added member referrals, gamification, profile customization, and a full rewards program integrated with a third-party vending platform.

Where design has the most impact

This project reinforced where design has the most impact. Not just in the screens, but in how decisions get made. Helping a team converge. Giving developers enough context to build with confidence. Testing assumptions with real members. Making tradeoffs explicit so the product can ship. The platform tradeoff was the call that taught me the most: choosing to ship a strong iOS experience on time rather than a mediocre experience on both required the conviction to stand behind an imperfect launch.

← Back to all work
Invoca Call Review Console preview

Let's
talk.

Open to Senior or Staff UX design roles in enterprise, AI, or consumer. Available now.