Plate 02 — Independent UX Research · Hinge · 2025
Why dating-app users disengage — and a prototype that responds.
I conducted an independent UX research study with 43 male Hinge users aged 32–57. Through three open-ended questions, I explored what creates frustration, uncertainty, and disengagement in the dating-app experience. The findings were synthesised into five themes and translated into prioritised product directions and an interactive prototype.
- Role
- UX researcher & product designer
- Method
- Qualitative interviews
- Participants
- Male Hinge users
- Output
- Themes + prototype
- Focus
- Retention friction
- Status
- Independent concept
01 — Why this study
Curiosity, not a brief.
Dating apps are emotionally intense product environments: people use them often, but frustration builds quickly when the system feels opaque or conversations go nowhere.
I wanted to move beyond generic complaints and understand the specific moments where Hinge users lose trust, lose momentum or disengage from the experience.
The study was exploratory rather than representative. Its purpose was not to make market-wide claims, but to identify recurring experience patterns and product opportunities worth testing through a focused prototype.
Because the participant group was limited to male users aged 32–57, the findings are directional and should not be generalised to the entire Hinge user base. The prototype therefore represents an exploratory concept rather than a final product recommendation.
43
Participants
3
Open-ended questions
5
Synthesised themes
1
Interactive concept
02 — Problem
The issue was not only matching. It was meaning.
Distilled from user feedback
Users do not always understand why certain profiles are shown to them, and many feel stuck when conversations receive no visible feedback. As a result, matches feel arbitrary, messages feel risky and users gradually disengage.
03 — Themes
Five coded themes showed where the experience breaks.
01
Messenger limitations
Users wanted richer interaction: multiple photos, quick video-call invites, message editing and a way to revisit past profiles.
25%
coded mentions
02
Filtering & likes
Users wanted more filtering options around shared interests and lifestyle. Paying for basic refinement felt frustrating.
23%
coded mentions
03
Profile & matching
Users wanted deeper profile fields and compatibility cues, but also felt discouraged when matches led nowhere.
23%
coded mentions
04
Algorithm transparency
Users did not understand why certain profiles were shown and suspected the app prioritised appearance over compatibility.
15%
coded mentions
05
UI & usability
Small interaction frictions appeared repeatedly: hidden actions, location confusion, notification behaviour and basic flow issues.
10%
coded mentions
04 — Product decisions
I did not design every request. I chose the retention levers.
In scope
- 01
Match transparency card
A short explanation attached to a profile: shown because of shared interests, lifestyle signals or profile context.
- 02
Conversation starters
Suggested openers based on the receiver's prompts, designed to reduce the blank-message problem.
- 03
Soft response signal
A gentle seen/stale indicator that reduces uncertainty without turning emotional communication into pressure.
- 04
Free filter chips
Basic shared-interest and lifestyle filters that feel like core matching support, not a premium punishment.
Out of scope
Video-call invites
Potentially useful, but too heavy for the first concept direction.
Message editing
A valid usability issue, but weaker as a retention lever.
Compatibility quizzes
Promising, but large enough to need a separate research cycle.
Algorithm overhaul
Outside the realistic scope of an independent UX concept.
05 — Prototype
Three concept screens, each tied to one insight.
Why this profile
Shown because
Suggested opener
Their prompt
Soft signal
Seen 2 days ago
Prototype logic
The prototype does not try to make dating effortless. It makes the system feel more explainable, and the first message feel less like a blind risk.
06 — Reflection
What this taught me about product judgement.
01
Insights without prioritisation become decoration.
02
A strong problem statement is shorter than the research behind it.
03
Transparency can be a product feature, not just a policy statement.
04
Soft signals work better than hard states in emotional interfaces.
05
Saying no to a requested feature is part of the design work.
06
Independent research is a practical way to build product judgement.