Product pattern

Dark patterns

Interface designs that trick, pressure or obstruct users into choices that benefit the company and that they would not otherwise make.

Dark patterns The same upgrade offer drawn twice. The dark version has a countdown that is not real, a guilt-trip decline link and a close button that is almost invisible. The honest version has a real end date, a plain No thanks button and a clear close button. Pushes you into yes Offer expires in 04:59 Go Premium $59.99 a year Claim my discount No thanks, I hate saving money 1 2 3 Lets you decide Sale ends 30 June Go Premium $59.99 a year Start Premium No thanks 1 2 3 1 Is the deadline real? 2 Is saying no guilt-free? 3 Can you see the way out? Converts more today, costs refunds, churn and trust
One upgrade offer twice: a fake countdown, a guilt-trip decline link and a faint close button, next to a real end date, a plain No thanks and a clear exit.

Dark patterns (also called deceptive patterns) exploit the same biases good design works with, but against the user's interest. On this site the examples are confirmshaming (guilt-trip copy or a crying emoji on the decline option), hidden exits (the only skip link tucked into a grey footer), and artificial urgency (a countdown on a "reserved" discount that has no real deadline).

Colin Gray and colleagues (CHI 2018) sorted practitioner examples into five strategies: nagging, obstruction, sneaking, interface interference and forced action. Arunesh Mathur and colleagues (CSCW 2019) crawled about 11,000 shopping sites and found 1,818 dark-pattern instances, including fake countdown timers, with 183 sites using outright deceptive claims. Jamie Luguri and Lior Strahilevitz (2021) tested them on a large US sample: mild dark patterns roughly doubled sign-ups for a dubious service and aggressive ones nearly quadrupled them, though aggressive versions also produced a strong backlash.

Paywalls and consent screens are where these show up most, because they sit at the money and data decisions. They lift short-term conversion and cost refunds, churn, reviews and, increasingly, regulatory risk.

How to use it

  • Give the decline or skip option the same visibility as accept, in a predictable place, with neutral wording.
  • Use timers and scarcity only when the deadline or limit is real and enforced.
  • Test each paywall or consent screen by asking: would the user still make this choice if they fully understood it?

Watch out

  • Treating "it converts" as proof a pattern is fine; the lift often comes from mistakes users later reverse or resent.
  • Small copy choices add up: a guilt-laden decline link plus a preselected add-on plus a faint close button is a dark flow even if each piece seems minor.

Related

Dark patterns in real products 0 working · 3 not