Case Study · UX Research · Mobile App

Are you hangry
for hangouts?

A research-led UX project exploring how constraints like time, budget, and availability impact real-world social planning—and how thoughtful design can make connection feel possible again.

Hangly welcome screen
Hangly Bento dashboard
Hangly group creation screen
Hangly hangout creation flow
Project Hangly—social planning app
Role UX Researcher & Designer (solo)
Deliverables Research · Persona · Journey Map · Wireframes · Prototype
Course Product Design Strategy

Reducing friction in social planning

I want to see my friends more—I just don’t know how to make it happen.

Social connection is important, but planning time with friends has become unexpectedly difficult. Through user research, I discovered that the challenge is not a lack of motivation, but the cognitive and emotional burden of coordination.

Rui, a 33-year-old student and recent immigrant to Vancouver, wants to spend more time with her friends but often avoids initiating plans. Conflicting schedules, budget concerns, scattered tools, and the pressure of making decisions for a group frequently cause plans to fall apart before they happen.

Over time, this leads to missed connections and growing frustration—an experience shared by many people navigating busy adult lives, new cities, or tight budgets.

The work that follows reframes this challenge as a design problem: how do we lift the planning load off the people who already feel it the most?

How might we…

help Rui coordinate hangouts that fit everyone’s availability, budget, and preferences—without making planning feel difficult or exclusionary?

Meet Rui

Rui was developed into a primary persona, capturing her goals, constraints, emotional drivers, and pain points. The project was grounded in qualitative, user-centered research, beginning with a detailed interview with Rui and expanding into synthesis and analysis.

Profile photo of Rui Hu
Primary persona

Rui Hu

  • Female, 33 years old
  • Student, former Graphic Designer
  • Recent immigrant from Wuhan, China to Vancouver
  • Values: connection, affordability, ease

“It shouldn’t be this hard to spend an afternoon with my friends.”

Goals

  • Stay connected with friends & family
  • Find new experiences for her social groups
  • Find outings that are budget-friendly

Primary pain points

From “I want to hang out”
to “maybe next time.”

A journey map documented Rui’s experience from initial intent through disengagement, highlighting where friction and emotional drop-off occurred.

01 · Motivation

Rui wants to hang out with her friends.

“It’s been a while since we’ve all gotten together.”

02 · Coordination

She sends a group message to see who’s free.

“I’ll message everyone to see who’s free.”

03 · Frustration

Friends reply with conflicting times and budgets. Rui starts searching for activities.

“This shouldn’t be this hard!”

04 · Reflection

Rui gives up and stays home alone.

“Forget it—maybe next time.”

Storyboard illustrating Rui’s social planning experience

Storyboard documenting Rui’s end-to-end planning experience—the moments where momentum stalls.

User journey map visualizing Rui’s experience

Journey map showing motivation, coordination, frustration, and reflection—with opportunities surfaced at each stage.

What’s already out there?

Existing apps such as TimeTree, WhenAvailable, and Howbout were reviewed to identify what options are available and what gaps could be explored to better serve our target user.

TimeTree app screenshot
Collaborative calendar

TimeTree

  • Multiple shared calendars (family, work, personal)
  • Event comments and memos
  • Public calendars
  • Optional premium features
WhenAvailable app screenshot
Poll-based scheduling

WhenAvailable

  • Create date/time polls
  • Invite via link, no account required
  • Automatically finds the best time
  • Calendar holds and sync
Howbout app screenshot
Social calendar for friends

Howbout

  • Combines scheduling with social features
  • Shows availability with chat and reactions
  • Group plans, recurring events, countdowns
  • Customization and privacy controls

Shared / common features

  • Group scheduling: shared calendars or invited groups
  • Event creation: details, notes, and reminders
  • In-event communication: chat or comments
  • Notifications and updates
  • Cross-platform sync across iOS, Android, and web

Missing features that would address Rui’s needs

  • Events still need to be added manually—integrations with social platforms or event sources could reduce friction and eliminate yet another download.
  • While many tools handle availability well, none treat budget as a core factor when discovering or selecting activities.

Three rules that guided every decision

Insights from research were translated into principles that kept the project focused on real-world constraints rather than ideal scenarios.

01

Constraints first

Designing around reality, not ideal scenarios. Time, budget, and availability shape every flow before features do.

02

Planning should feel quieter

Less cognitive load, fewer decisions. Every step removed from the user is a step closer to actually meeting up.

03

Inclusion by default

No one should have to explain their limits. Budget and availability are baked in, not awkward conversations.

Reframing needs as jobs

Rui’s needs were reframed as jobs—concrete things she needed to accomplish. If something added pressure, complexity, or social discomfort, it didn’t belong in the solution.

01

When I want to spend time with friends, help me see overlapping availability so I can suggest a time that already works for the group.

02

When I’m planning an outing, help me navigate budget constraints so no one feels excluded or pressured to spend more than they’re comfortable with.

03

When I’m organizing a hang, keep all the details in one place so I’m not jumping between chats, calendars, and search results.

04

When friends reply, surface decisions and confirmations clearly so I know the plan is actually happening—not just being talked about.

Sketching out the entire flow

Before testing, I created paper prototypes to explore structure and flow. This low-fidelity stage allowed rapid iteration and ensured the experience aligned with Rui’s mental model.

Paper sketch of onboarding flow
Paper sketch of group selection
Paper sketch of hang creation
Paper sketch of confirmation flow

Sketching at very low fidelity made it easier to focus on flow instead of features. I could see where decisions stacked up, where things felt unclear, and where the experience needed to slow down or simplify.

1

Start a hang

Entry point into planning

2

Select a friend group

Keeps planning scoped and manageable

3

Set constraints

Availability, budget, and preferences come first

4

View suggestions

Only options that fit the group are shown

5

Confirm the plan

Clear next steps for everyone involved

Bento layout sketch for Hangly dashboard

Bento-grid sketch—an early dashboard concept where overlapping availability, RSVPs, and reminders share a single view.

What prototyping revealed

Prototypes were tested using scenario-based tasks—creating a group, setting criteria, browsing suggestions, and confirming attendance. Feedback informed multiple rounds of iteration.

Onboarding simplified after testing

Early prototypes asked for too much up-front. Through testing I removed and reordered steps so users could get to the dashboard quickly—with availability, budget, and preferences set early to reduce backtracking later.

  • Step-by-step setup with optional contact syncing
  • Constraints captured early, not retroactively
  • Confirmation states made plans feel real, not theoretical
Welcome screen
Preferences setup
Add friends step
Planning steps
Back-and-forth messages
Confidence initiating plans
Missed details

Hangly: a social planner that quiets the load

The final solution is a social planning app designed to reduce coordination friction and support inclusive decision-making—built around three core experiences.

Get set up—without giving up

  • Step-by-step setup with optional contact syncing to reduce initial effort
  • Users set availability, budget, and location early, allowing suggestions to fit everyone
  • Friendly defaults so a new user can start using the app immediately
Create account screen
Set preferences
Enable notifications

One place for plans, people, and pings

  • All information, reminders, and updates live in one shared place
  • Planning happens within defined groups, reducing scheduling conflicts and decision fatigue
  • Gentle nudges surface moments of overlapping availability to encourage follow-through
  • Users can create as many groups as they like—from two people to a full crew
Bento dashboard
Group creation step 1
Group creation step 2

Plans that confirm themselves

  • External calendar syncing reduces no-shows and confusion
  • A map shows overlapping availability to clarify which options work for the most members
  • A custom RSVP countdown gently encourages group members to confirm in a timely manner
  • Suggestions match the group’s budget by default—no awkward conversations needed
Hang creation flow
Hang creation suggestions
RSVP confirmation screen

What testing told us

While this project did not reach full market deployment, testing and feedback revealed meaningful outcomes about how the design changed the planning experience.

+

Users found onboarding clearer and less intimidating

+

Planning within friend groups reduced perceived effort

+

Budget visibility increased confidence and inclusion

+

Timely prompts improved follow-through

+

Calendar syncing reduced missed plans

+

Users reported that planning felt “lighter” and more manageable

From stressful responsibility to supportive background process

Hangly transformed planning from a stressful responsibility into a supportive background process—helping users turn intention into action.

What worked well

  • Letting research lead the solution
  • Using JTBD to focus on real user work
  • Treating constraints as design inputs
  • Prototyping early and often

Challenges

  • Balancing simplicity with feature depth
  • Streamlining the onboarding process
  • Avoiding over-engineering early concepts
  • Designing for emotional friction, not just usability

Areas for improvement

  • Expanded accessibility options
  • Smarter AI-driven suggestions over time
  • Deeper integrations with external event platforms
  • Continued iteration based on real-world usage

Hangly did not begin as an app idea. It began by listening. By centering Rui’s experience and designing around real-life constraints, Hangly demonstrates how thoughtful UX can reduce friction, support inclusion, and make connection feel possible again.

Next Project

CuePo

UX / Product Design · Smart rewards for better training

Read case study →