Skip to main content
UI Coach Logo
Back to challenges
Hard

Share a Dating Safety Check-In

Design an opt-in safety check-in that lets a dater share limited plans with a trusted contact and decide what happens after a missed response.

Mobile

The brief

Understand the problem

Background

Sharing date plans can help someone feel supported, but continuous tracking can create new privacy and coercion risks. A useful check-in needs consent, minimal data, an explicit escalation plan, and a quick way to end sharing.

User context

Leila is meeting someone new at a cafe. She wants her friend Noor to know the venue and receive a prompt if Leila misses a 10:30 PM check-in, but she does not want live location shared throughout the date.

Product problem

A dater needs a flexible safety plan that a trusted contact can act on without the product implying surveillance, guaranteed rescue, or automatic danger detection.

Objective

Create plan setup, trusted-contact consent, active check-in, and missed-response handling for one date.

What to design

Define the experience

Required experience

  • Choose what plan details to share and for how long
  • Invite a trusted contact who explicitly accepts the role
  • Confirm safety, extend the plan, or request help discreetly
  • Handle a missed check-in using the agreed contact steps

Screens and states

  • Safety plan setup
  • Trusted contact acceptance
  • Active check-in
  • Missed response guidance

Core user flow

Follow the critical path

  1. 01

    Leila enters the cafe, expected end time, and a short note about her date

  2. 02

    She invites Noor and reviews exactly what Noor will see

  3. 03

    Noor accepts and confirms the agreed first response is a text message

  4. 04

    Leila extends the plan once and later misses the new check-in

  5. 05

    Noor receives the agreed context and step-by-step options without a claim that harm occurred

Product rules

Requirements and constraints

Requirements

  • Use data minimization and make every shared field visible before activation
  • Require the trusted contact to accept responsibilities and communication preferences
  • Offer discreet controls to confirm, extend, end, or request immediate help
  • Let the dater stop sharing at any time and show what records remain
  • Provide local emergency and specialist resources without presenting the app as an emergency service

Constraints

  • Live location is optional and off by default
  • A missed response alone cannot be labeled as an emergency
  • Push delivery and mobile connectivity are not guaranteed

Reality check

States worth considering

The trusted contact does not accept before the date
The dater loses connectivity near check-in time
The trusted contact may be a source of coercion
The dater changes venue without wanting to reveal a precise route

Finish line

What to deliver

  • Four mobile screens showing consent-based setup, active controls, and a missed check-in response

Optional direction

Visual resources

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

Color palette
#79674F
#EDE6D2
#090C0F
#B7B7B7
#A7A7A7
Font pairing
CardoJosefin Sans

Cardo & Josefin Sans

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

Icons
Illustrations