Heartline — Making Real Friends Without the Awkwardness

Heartline is a low-pressure social interface prototype designed to help Northeastern students bridge online discovery into real-life meetups, reducing awkwardness and emotional risk through trust, clarity, and interest-based connection.

Needfinding Task Analysis Lo-Fi → Hi-Fi User Testing Iteration Privacy
POV: Northeastern students who feel socially isolated need a low-pressure way to move from online interaction to real-world, in-person connection, because fear of awkwardness and social missteps prevents them from taking the first step.

1) Problem & Why it Matters

Students are physically surrounded by peers yet still experience loneliness and social anxiety. Many platforms encourage performance and passive connection rather than genuine in-person friendship.

  • Design goal: reduce social “activation energy” to start a friendship
  • Principle: psychological safety + low cognitive load
  • Bridge: discover → invite → meetup (low-stakes)

2) Approach

We focused on reducing hesitation and uncertainty before a user takes social action. That means clear next steps, trust signals, and low-pressure group entry rather than forcing one-on-one cold approaches.

  • Trust: identity verification + mutual acceptance before chat
  • Discovery: nearby users and interest-based groups
  • Coordination: map-based meetup context

3) Needfinding & Task Analysis

Task analysis revealed much of the “work” happens before anyone speaks: scanning, risk evaluation, and fear of embarrassment. We designed the interface to intervene early by lowering emotional barriers and decision fatigue.

  • Requirement: reduce perceived emotional risk when initiating interaction
  • Requirement: enable zero-prep participation (fast to first action)
  • Metric idea: Time-to-First-Interaction (TTFI) + follow-through rate

4) System Concept

Heartline explores a simple structure: verified identity for trust, map-based discovery to make nearby connections actionable, and groups to reduce the pressure of one-on-one initiation.

  • Verification: student ID/documents
  • Map: nearby users + meetup context
  • Groups: topic + capacity + location
  • Communication: chat + voice

5) Low-Fidelity Prototyping

We translated early ideas into paper screens to quickly test the interaction flow. These sketches focused on the highest-impact actions: discovering nearby people, joining groups, verifying identity, deciding on location sharing, contacting another user, and managing an account.

  • Discovery: map-based browsing of nearby users and shared interests
  • Connection: low-pressure actions (Join, Chat, Voice)
  • Trust: student verification and location-sharing decisions
  • Coordination: route/map concepts for meetups
  • Control: settings and contact list for longer-term use

Why Lo-Fi mattered

Lo-fi helped us spot hesitation points before investing in hi-fi visuals. It also helped validate whether the product still felt “low pressure” while supporting real-life meetups.

  • Clarity: do users know what to press next?
  • Trust: do users understand verification/location implications?
  • Discoverability: can users find map, groups, and actions quickly?

7) Hi-Fidelity Prototype (Figma)

Embedded Figma prototype. If it doesn’t load, make sure Figma sharing is set to “Anyone with the link can view”.

8) Testing Findings

Low-fi and hi-fi testing surfaced consistent friction points: unclear feedback after actions, map/navigation ambiguity, verification expectation gaps, and missing discoverability cues.

  • No feedback after actions: users unsure invite sent / group joined → confirmation states (✓)
  • Navigation & map confusion: users tapped wrong tabs or didn’t realize map was interactive → onboarding cues
  • Verification expectation gap: requirements felt sudden → clearer ID explanation + progress indicator
  • Discoverability: missing/weak search and key actions → add search + clearer CTAs
  • Engagement: group creation needed a clear CTA

9) Iterations

  • Clarity & discoverability: stronger CTAs, improved profile hierarchy
  • Trust & transparency: step-by-step verification flow + progress feedback
  • Interaction & navigation: map cues (markers/hints) and improved tab structure
  • Engagement: add search bar, “Create Group”, and separate New vs Joined groups
Key takeaway: Designing for friendship means designing for trust, clarity, and emotional safety—not just adding more social features.

10) What’s Next