Mobile App • Concept 2025
Bond Beyond
Bond Beyond
Designing intentional connection for long-distance friendships
Role
Product Design
TIMELINE
12 weeks
SKILLS
UX Design
Product Strategy
User Research
TEAM
3 Product Designers
2 UX Researchers
OVERVIEW
OVERVIEW
A group chat isn't a friendship. Neither is a birthday text. Long-distance friends feel the difference, their apps don't. Everything's built for messaging frequency, not the slow work of staying close.
Bond Beyond is a 12-week project: async threads replace chat, shared availability replaces calendars, lightweight events form when free time overlaps. No streams, no read receipts, no engagement metrics. This case study covers the visual, and research decisions I owned
A group chat is not a friendship. Neither is a birthday message. Long-distance friends know the difference, but the apps they use don’t — everything’s built for messaging frequency, not the small, slow work of staying close.
Bond Beyond is a 12-week concept project: a mobile app built around async threads instead of chat, shared availability instead of calendars, and lightweight event creation when free time overlaps. No streams, no read receipts, no engagement metrics. This case study focuses on the visual and interaction decisions I owned
PROBLEM STATEMENT
PROBLEM STATEMENT
Staying connected is easy. Staying close is not.
Staying connected is easy. Staying close is not.
The friction isn't messaging, it's what happens around it. Time zones turn "are you free this week?" into a week-long back-and-forth. Weeks pass and starting a real conversation starts to feel like it needs an occasion. Group chats stay alive but say nothing.
The friction isn’t messaging, it’s what happens around it. Time zones turn “are you free this week?” into a back-and-forth. Weeks pass and starting a real conversation feels like it needs an occasion. Group chats stay alive but say nothing.
USER RESEARCH
USER RESEARCH
We studied long-distance friendships to find where connection breaks down.
We studied long-distance friendships to find where connection breaks down.
Scope: 5 interviews (mostly international students navigating time-zone gaps, plus a few domestic pairs), benchmarked against Marco Polo and Cappuccino, the closest existing products. Synthesized via affinity mapping in FigJam.
Scope: 5 interviews (mostly international students navigating time-zone gaps, plus a few domestic pairs), benchmarked against Marco Polo and Cappuccino, the closest existing products. Synthesized via affinity mapping in FigJam.
*All the research steps conducted on figjam*
The hypothesis held: time-zone coordination and post-silence reconnection were consistent pain points, and existing apps optimize for volume, not for a specific friendship. It also sharpened decisions we hadn't made yet - availability needed to stay broad and ambient rather than precisely scheduled, threads beat streams for reconnection, and the product needed to actively resist streaks and notification hooks.
Caveat: five interviews and two benchmark apps are enough to pressure-test a direction, not enough to make category-wide claims. Every pattern here is directional
What it confirmed. Time-zone coordination was a recurring pain point. Reconnecting after weeks of silence carried real emotional weight. Existing apps weren’t broken, they were built for volume, not for the specific work of maintaining a friendship. The hypothesis held.
What it refined. Interviews sharpened design specifics we hadn’t decided going in, that availability needed to be broad and ambient, not precise scheduling; that threads worked better than streams for the reconnection problem; that the app needed to actively design against notification hooks, streaks, and other engagement patterns competing for the same emotional real estate.
What we can’t claim. Five interviews and a two-app benchmark is enough to pressure-test a design direction, not enough to make category claims about long-distance friendship broadly. The Marco Polo and Cappuccino comparison was deliberately narrow, those were the closest overlapping products, not a full landscape scan. Any pattern we saw is directional.
DESIGN DECISIONS
DESIGN DECISIONS
Early concepts revealed where the experience
broke down
Early concepts revealed where the experience
broke down
We tested early concepts and mid-fidelity flows to check whether the experience felt intuitive and emotionally approachable. Users understood the intent, but three points of friction surfaced:
Users weren't always sure where to start or what action to take first.
Some UI elements lacked visual hierarchy, making flows feel unclear.
The relationship between prompts, availability, and events wasn't immediately obvious.
We tested early concepts and mid-fidelity flows to check whether the experience felt intuitive and emotionally approachable. Users understood the intent, but three points of friction surfaced:
Users weren't always sure where to start or what action to take first.
Some UI elements lacked visual hierarchy, making flows feel unclear.
The relationship between prompts, availability, and events wasn't immediately obvious.
*Before vs After*
WHERE WE LANDED
WHERE WE LANDED
Design decisions focused on clarity, hierarchy, and emotional ease
Design decisions focused on clarity, hierarchy, and emotional ease
We used these insights to guide the final direction: simplifying navigation, strengthening hierarchy, and clarifying how features connect across the experience.
How the design evolved:
Reworded prompts and added a clearer visual cue for starting a chat, replacing an ambiguous entry point
Elevated the mid-fi screens into a defined visual hierarchy — deliberate type scale, spacing, and weight instead of near-uniform mid-fi styling
Refined navigation connected prompts, availability, and events into one cohesive experience
This resulted in a final experience that felt calmer, more intuitive, and easier to return to over time.
We used these insights to guide the final direction: simplifying navigation, strengthening hierarchy, and clarifying how features connect across the experience.
How the design evolved:
Reworded prompts and added a clearer visual cue for starting a chat, replacing an ambiguous entry point
Elevated the mid-fi screens into a defined visual hierarchy — deliberate type scale, spacing, and weight instead of near-uniform mid-fi styling
Refined navigation connected prompts, availability, and events into one cohesive experience
This resulted in a final experience that felt calmer, more intuitive, and easier to return to over time.
SOLUTION
SOLUTION
A space built to maintain the bond, not maximize engagement.
A space built to maintain the bond, not maximize engagement.
Bond Beyond brings guided conversations, shared availability, and lightweight planning into one app, helping long-distance friends stay emotionally close without relying on constant messaging.
The experience prioritizes presence over interaction, making it easier to reconnect intentionally across distance and changing routines.
Bond Beyond brings guided conversations, shared availability, and lightweight planning into one app, helping long-distance friends stay emotionally close without relying on constant messaging.
The experience prioritizes presence over interaction, making it easier to reconnect intentionally across distance and changing routines.
*This resulted in a final experience that felt calmer, more intuitive, and easier to return to over time*
CORE FLOWS
CORE FLOWS
Creating a thread
Starting a meaningful conversation across distance can feel awkward.
Prompt-based threads remove that friction, giving friends a thoughtful starting point they can pick up at their own pace.
Creating a thread
Starting a meaningful conversation across distance can feel awkward.
Prompt-based threads remove that friction, giving friends a thoughtful starting point they can pick up at their own pace.
Replying to a thread
Threads hold a conversation open over time instead of demanding an instant reply.
Friends respond in text, images, audio, or video whenever they're free.
Setting availability
Availability replaces back-and-forth scheduling with visibility. Friends see overlapping free time across time zones instantly, so planning stops feeling like work.
Setting availability
Availability replaces back-and-forth scheduling with visibility. Friends see overlapping free time across time zones instantly, so planning stops feeling like work.
Creating event
Connection shouldn’t require perfect planning.
When friends are free at the same time, availability can turn into a shared moment.
Creating event
Connection shouldn’t require perfect planning.
When friends are free at the same time, availability can turn into a shared moment.
IMPACT
IMPACT
What I took from this project
What I took from this project
Designing for long-distance friendships taught me to design for less: less friction to start, less coordination to plan, less activation energy to return. The real impact wasn't more features — it was clarity, pacing, and restraint built into every decision.
Designing for long-distance friendships taught me to design for less: less friction to start, less coordination to plan, less activation energy to return. The real impact wasn't more features — it was clarity, pacing, and restraint built into every decision.