Skip to main content
UI Coach Logo
Back to challenges
Hard

Consent Based Interest Matching

Design an opt-in dating discovery flow that matches people through shared interests without importing private social graphs.

Mobile

The brief

Understand the problem

Background

Shared interests can make introductions easier, but scraping friends, likes, or outside accounts removes consent and can reveal sensitive relationships. A safer product relies on information each person chooses to share.

User context

Eli wants to meet someone who enjoys tabletop games and small live music venues. He is comfortable selecting interests but does not want the service reading contacts or posting activity elsewhere.

Product problem

The experience must explain why a match appears, prevent interest labels from becoming rigid stereotypes, and support safety before an in-person meeting.

Objective

Create onboarding, match explanation, conversation consent, and meeting safety for an interest-led dating app.

What to design

Define the experience

Required experience

  • Privacy-aware profile setup
  • Explainable match discovery
  • Mutual conversation start
  • Safe meeting planning

Screens and states

  • Interest and privacy setup
  • Match detail
  • Conversation request
  • Meeting safety tools
  • Block and report

Core user flow

Follow the critical path

  1. 01

    Eli selects interests and visibility settings

  2. 02

    He reviews a match and the shared signals

  3. 03

    Both people agree to start a conversation

  4. 04

    They plan a public meeting and share the plan with a trusted contact

Product rules

Requirements and constraints

Requirements

  • Use only explicitly provided profile data
  • Explain matching signals without exposing private attributes
  • Require mutual consent before messaging
  • Offer blocking, reporting, and meeting safety controls
  • Allow any interest to be hidden

Constraints

  • No contact list or social account scraping
  • Sensitive attributes cannot be inferred
  • Location must remain approximate before trust is established

Reality check

States worth considering

A match withdraws consent
Someone sends harassment
A user sees a known person
A profile misrepresents identity
A meeting plan changes

Ready-to-use content

Mock data

Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.

Shared interests

  • Cooperative board games
  • Independent concerts
  • Weekend museum visits
  • Prefers quiet first meetings

Finish line

What to deliver

  • Five mobile screens or states
  • A privacy explanation for every data source used in matching

If you want more

Optional extensions

Add community-hosted interest events
Design an identity verification choice

Optional direction

Visual resources

Use these as a starting constraint if you want one. They are not part of the required solution.

Color palette
#1C1B19
#C7B89F
#649853
#735D5F
#87759D
Font pairing
Julius Sans OneCrimson Text

Julius Sans One & Crimson Text

Clear interface writing gives people the confidence to understand what changed and decide what to do next.

Icons
Illustrations