Category:
Mobile Design
Client:
Indiana University
My Role
UX & Interaction Design
Duration
4 Months From Jan'25 to Apr'25
Methods
Design: Rapid Prototyping, High-Fidelity Prototyping, Usability Testing
About Haven
Haven is a peer-to-peer community platform designed to make it easier for people to give and receive help within their local circles. As part of the design team, I led the onboarding redesign to make the first-time experience feel intuitive, trustworthy, and meaningful helping users understand why Haven exists before they start engaging.
The Findings
Through internal analytics and early user feedback, three main friction points surfaced:
target audience limited
No space for users who do not have a code. thy are left starnded
Low Trust at Entry
Community-based apps need to feel credible, users were hesitant to share personal details without clarity on use. asking so many details at first before they even understand what haven in and decide if they wan tot use it
Unclear Path After Joining
what to do now that we have joined haven
Research Goals
Inviting:
Emotionally warm and simple
Grounded:
Builds understanding and trust early
Motivating
Connects sign-up to a small, meaningful action
Identifying Use Cases
Through user research and stakeholder interviews, we identified three primary entry points for new users:
Have an Access Code
Users invited by existing members with a unique access code to join their specific Haven community.
B. Join Public Haven - the courtyard experience
Users discovering open Haven communities through search or recommendations, able to join instantly.
C. Join Waitlist
Users who want to start their own haven
Iterations and Feedback (Important One's)
Iterations 01: Screen Refinements
Early in the process, I focused on defining the right entry logic for Haven’s onboarding.
Multiple flow versions were explored to understand how users transition between access types — invite-only and waitlist. Each flow was tested internally to assess clarity, emotional tone, and system scalability.
Early in the process, I focused on defining the right entry logic for Haven’s onboarding.
Multiple flow versions were explored to understand how users transition between access types — invite-only and waitlist. Each flow was tested internally to assess clarity, emotional tone, and system scalability.
Iterations 02: Flow Refinements
too much information
waiting time approval - users cannot do anything
profile completion - after the signup - too many steps
waitlist felt secondary
Things changed:
shifted all fields form first and then select haven
added public haven so that they can explore till approval is done
problems:
our main current user are with invite code are not ptiotised
too many steps before giving them value
Proposed Solution
Use Case 01: Haven Code
This flow simplifies how users with access codes join private Havens. It minimizes friction through auto-filled invite links, clear prompts, and transparent review steps.
A trust-based entry flow that feels secure yet lightweight, reinforcing Haven’s goal of safety and genuine membership.
Profile Setup
This flow personalizes the onboarding experience by helping users present themselves authentically before joining a Haven.
Each screen focuses on trust, self-expression, and connection — three foundational principles gathered from user interviews and stakeholder alignment sessions.
Use Case 02: Join Public Haven
This design supports open exploration and community discovery for users who don’t have an invite. It uses spatial cues and accessible interaction patterns to make browsing intuitive and engaging.
A clear, visual browsing experience that helps users explore, compare, and request access to new Havens with minimal cognitive effort.
Use Case 03: Waitlist
This flow ensures transparency and warmth for users awaiting approval. Instead of a static confirmation screen, the design uses human-centered feedback and continued engagement opportunities.
A thoughtful waiting experience that reassures users, sets expectations, and maintains engagement within the platform.
Prototype
Each flow was designed to reduce friction, support transparency, and reinforce Haven’s sense of belonging. From profile setup to access-specific paths, the final iterations bring consistency to the entire onboarding experience.
Challenges
Designing Haven's onboarding reaffirmed that trust and clarity matter more than speed in community-based products. A seamless flow means little if users don't emotionally connect to the purpose.
1
Context First, Action Second
Users need to understand "why" before they commit to "how." Building emotional alignment early is crucial for community products.
2
Test Early, Test Often
Assumptions about what users value can be wrong. What seemed "obvious" to us (like points) actually confused users until properly contextualized.
3
Design for Belonging
By framing each step as part of joining a community rather than just completing a form, we turned onboarding into the first act of participation.
UX Consideration within Constraints
Designing Haven's onboarding reaffirmed that trust and clarity matter more than speed in community-based products. A seamless flow means little if users don't emotionally connect to the purpose.
Impact
Designing Haven's onboarding reaffirmed that trust and clarity matter more than speed in community-based products. A seamless flow means little if users don't emotionally connect to the purpose.
Reflection & Learnings
Designing Haven's onboarding reaffirmed that trust and clarity matter more than speed in community-based products. A seamless flow means little if users don't emotionally connect to the purpose.
1
Context First, Action Second
Users need to understand "why" before they commit to "how." Building emotional alignment early is crucial for community products.
2
Test Early, Test Often
Assumptions about what users value can be wrong. What seemed "obvious" to us (like points) actually confused users until properly contextualized.
3
Design for Belonging
By framing each step as part of joining a community rather than just completing a form, we turned onboarding into the first act of participation.