Designing a Support Community for Phones, Tired Eyes and Late Nights

When we opened the Patient Support Network, I assumed most members would join from a laptop at home. I was wrong. Almost four in five visits come from phones, and a surprising number of posts arrive between midnight and 4am, when worry is loudest and the surgery is closed.

That changed how I think about what a support community needs to be. Here is what we've learned so far. A reminder first: peer support is not medical advice, and our moderators point people to urgent care whenever a post sounds like an emergency.

Readable when you're exhausted

Large text, short paragraphs, plain words. Our members include people on strong medication, carers running on four hours' sleep and older people whose eyesight isn't what it was. If a page needs zooming, it's a barrier.

Quiet by default

Nobody in a hard week wants their phone buzzing every time someone likes a post. New accounts start on a daily digest, and people can switch more on once they're settled.

Privacy people can understand

• A private group for each condition, with approval to join.
• A plain note on every group page explaining who can see posts.
• The option to post anonymously in the most sensitive groups.

Help one tap away

Every page links to a "talk to a moderator" form and a short list of crisis lines. When someone writes at three in the morning, the first reply often comes from another member in a different time zone. That's the quiet magic of it: lanterns in the dark, held up by people who have been there.

If you build community software, I'd love to hear how you approach these things. And if you're a member who struggles with any of it, please tell us. We'd much rather fix it than lose you.