When Design Patterns End Up in Court

A court just ruled that Facebook and YouTube are liable for social media addiction. Not their algorithms in the abstract — their design choices. Infinite scroll. Autoplay. Notification systems engineered to pull you back. The patterns we've been debating in design circles for years are now being weighed in a courtroom.

That should make every product designer sit up a bit straighter this morning.

The reckoning is real

This isn't a slap on the wrist or a think-piece. It's a landmark legal finding that specific, deliberate UX decisions caused measurable harm. The court looked at the mechanics — the scroll that never ends, the video that plays before you've asked for it, the red badge that won't leave you alone — and said: these aren't neutral choices.

For years, we've talked about "dark patterns" as an ethical concern. Now they're a legal one.

What strikes me most is how ordinary these patterns are. Every designer reading this has built something with autoplay, or a notification system, or an infinite feed. The question was never whether these patterns work — of course they work, they're incredibly effective at driving engagement. The question is what "working" actually costs the people on the other end.

This verdict could force a genuine shift in how platforms approach engagement. But it should also prompt the rest of us — the designers building apps, tools, and sites that aren't Facebook — to think harder about the cumulative weight of our interaction choices.

The search box nobody trusts

Speaking of design decisions with consequences: here's a quieter one that affects almost every project. Site search is broken, and it's been broken for so long that users have given up.

There's a fascinating UX paradox at play. People will leave your site, open Google, and search for content that exists on your site rather than use your internal search. The "big box" wins every time, because it's fast, relevant, and reliable in a way that most on-site search simply isn't.

This isn't a technology problem. It's a design priority problem. We pour resources into homepage hero sections and onboarding flows, but site search — the thing users reach for when they're actually trying to do something — gets treated as an afterthought. A text field wired up to a basic query, maybe with some filters if you're lucky.

The lesson here is that findability is UX. If people can't locate what they need within your product, it doesn't matter how beautifully you've designed the thing they're looking for. The content might as well not exist.

Should that be a modal? Probably not.

On a more practical note, there's a useful new decision framework doing the rounds for one of design's most reliably contentious choices: when to use a modal dialog versus a full page.

Modals have become a reflex for a lot of teams. Need a confirmation? Modal. Editing something? Modal. Sign-up prompt? Modal. But the truth is, modals are often the wrong call — they interrupt flow, they're accessibility nightmares on mobile, and they frequently force complex tasks into a container that's too small for them.

The decision tree approach is refreshingly simple: consider the complexity of the task, the context the user needs, and how much interruption is actually warranted. If the answer to any of those is "a lot," you probably want a dedicated page.

I find this kind of structured thinking incredibly valuable — not because designers can't make these calls intuitively, but because having a shared framework makes it much easier to push back when a stakeholder says "just make it a modal" for the fifteenth time.

Tool spotlight: WordPress lets AI agents run your site

WordPress.com has introduced support for AI agents to manage and update sites. In theory, this means automated content management — AI handling publishing tasks, site tweaks, and routine maintenance.

I'm cautious about this one. The idea of handing site management to an AI agent sounds efficient until you think about all the small editorial and design judgements involved in running even a simple site. Which image goes where. How a headline reads. Whether a layout change actually improves the experience or just looks different.

It'll be interesting to see whether this becomes genuinely useful for solo publishers and small teams, or whether it introduces a new category of "AI did something weird to my site" support tickets. Worth watching, but I wouldn't hand over the keys just yet.

The bigger picture

Today's stories share an uncomfortable thread: the choices we make about how interfaces behave are never neutral. An infinite scroll isn't just a pattern — it's a decision about how much of someone's time and attention you're willing to consume. A broken search box isn't just a minor annoyance — it's a decision that your users' goals don't matter enough to invest in properly. A modal slapped onto a complex task isn't just a quick fix — it's a decision to prioritise your convenience over theirs.

The social media verdict makes this concrete in a way that's hard to ignore. Design decisions have real consequences for real people. That's always been true. Now a court agrees.

So what do you do with this?

Next time you're choosing a pattern — any pattern — pause and ask yourself the second-order question. Not just "does this work?" but "what does this encourage?" Not just "will users engage?" but "at what cost?"

Audit your site search. Rethink that modal. And take the social media verdict not as someone else's problem, but as a reminder that the details of interaction design carry more weight than we sometimes admit.

The courtroom just told us what we already knew. It's time to act like we believe it.