Alyne is a mobile app for social wellness booking and payments. It was designed to solve the messy coordination problems that come with booking wellness classes, especially when trying to schedule, split payments, and organize with friends. I designed Alyne to simplify the process; users can book solo or with friends, split payments seamlessly, and browse a social feed of wellness activities tied to real studios and local communities. The goal was to make booking feel collaborative, connected, and easy to return to.
Social Booking & Payments for Wellness
Client & Duration:
Alyne | 2025 April - 2025 June
Type:
Mobile Booking, Payment, and Local Commerce
My Role in Cross-Team Syncs:
- Collaborated with 1 PM, 1 front-end, and 2 back-end devs over a 6-week sprint
- Synced daily via Slack & Figma; weekly calls to align scope
With PM: Prioritized features based on user needs & feasibilityWith Engineers: Delivered annotated flows + async Looms for handoff
With Team: Led UI critiques to clarify edge cases and interaction logic
PROBLEM
The infrastructure of wellness hasn't caught up to how people actually experience it, socially, spontaneously, and together.
Coordinating boutique fitness and wellness classes with others is often clunky, with group texts, shared calendars, scattered links, and confusing payment splits. Existing platforms like Mindbody lack a modern social layer and feel outdated for today’s mobile-first wellness users.
SOLUTION
One flow for friends, payments, and plans
To solve those coordination headaches, we built Alyne, a social wellness booking and payment service that makes it easy to plan with friends. Users can invite others to join bookings, check their availability, and pay together. Payments are split seamlessly. So each person pays individually, and the group booking only locks in once everyone commits. Everything happens in one place, no more Venmo links, scattered text threads, or calendar screenshots.
IMPACT (In pilot testing of MVP)
+26%↑ in booking completion, driven by simplified group flows and split payment logic
2.3×↑ friend-invite usage, signaling early signs of social stickiness
21%↓ in no-shows and an increase in pre-class confirmations after adopting Alyne’s group booking flow
KEY FEATURES
A. Group booking + Split payments
Alyne simplifies group coordination by allowing users to book together, but confirm and pay independently. The booking only locks in when everyone commits, reducing flake risk and giving users clarity and control.
→ Result: 26% increase in booking completion and 34% faster confirmation time.
B. Intent-based discovery feed
The home feed surfaces intent, not just achievements. By showing friends’ studio activity, wishlists, and class plans, Alyne drives social discovery that feels authentic and motivating, without pressure to perform.
→ Result: “Wants to try” posts generated 2.3× more clicks to booking pages than passive scrolling.
C. Studio discovery, social, local, and actionable
Instead of filtering through endless anonymous listings, users explore studios based on real-world proximity, social signals, and shared intent, where friends go, what’s trending nearby, and which offers are actually relevant.
D. Booking transfer system
Life happens. Alyne lets users release their class to others when they can't make it, and easily claim shared spots from the community. It keeps classes full and the community flexible.
→ Result: Studios saw a 21% drop in no-shows
DESIGN APPROACH
1. Understanding the current behavior gap
Before jumping into UI, I mapped out how people currently coordinate wellness plans. Most relied on texts, calendar screenshots, separate booking platforms, and Venmo. The process wasn’t just fragmented; it failed to support shared intent or real-time clarity.
→ I interviewed 5 target users and created simplified journey maps to understand the moment friction happens (e.g., “who’s in?” stage).
2. Defining the core experience loop
From these insights, I defined Alyne’s core loop as "Discover → Coordinate → Commit → Show Up → Repeat". Booking wasn’t a button, but it was a behavioral chain. I prioritized flows that made that chain feel intuitive, social, and low-friction. That meant enabling flexible participation, shared payment, and status visibility at each step.
3. Interaction & flow design
Each flow was designed to reduce friction and reinforce trust at key decision moments. Low-fi wireframes were rapidly iterated with our PM and dev, then translated into scalable Figma components.
4. Validation & feedback
We ran lightweight tests through Figma prototypes + feedback from early users and studio owners. These early validations helped sharpen Alyne’s value prop without overbuilding.
- ✔️ Group booking flow: Users responded best to designs with clear confirmation and payment status
- ✔️ Discovery feed: “Wants to try” micro-interactions outperformed “likes” in intent tracking
- ✔️ Studio feedback: They loved the ability for users to release or share their bookings instead of ghosting
REFLECTION
From interface to interaction, what social UX demands
✔️ Split payments aren't just a UI problem, but they're about trust.
Users needed to understand who paid, who hasn’t, and what happens next. Clear payment status indicators reduced drop-offs by 38% post-invite.
✔️ Group booking requires behavioral design.
Simply adding friends to a booking wasn’t enough. I needed to reinforce shared intent through progress states, smart nudges, and status visibility.
✔️ Social feeds are most powerful when they reflect intent, not performance.
“Wants to try” posts outperformed traditional likes because they gave users a low-pressure way to express interest and start a plan.
✔️ Shipping for real behavior means compromising perfectly clean flows.
Sometimes, showing just enough friction (like confirmation delays or opt-ins) created better outcomes than over-automating.