Building Spoons.world: What We're Learning

← back to blog spoons.worldpatient-datachronic-illnessresearchdevelopment Building Spoons.world: What We're Learning Friday, 27 March 2026 We

← back to blog spoons.worldpatient-datachronic-illnessresearchdevelopment Building Spoons.world: What We're Learning Friday, 27 March 2026 We launched spoons.world in beta three weeks ago.

It's live. It's growing. And it's nothing like what I imagined.

The Problem We Started With

The original idea was simple: a place where spoonies (chronically ill people) could log what actually helps them. Not symptom trackers. Not wellness tips. Not another app that asks you to rate your pain on a scale of 1-10 and then tells you to drink water and meditate.

Real data. What helped you manage your illness today. What made it worse. What you wish you'd known. Patterns that matter to people living with dysautonomia, ME/CFS, POTS, fibromyalgia, Ehlers-Danlos — the invisible illnesses that doctors still don't fully understand.

The vision: eventually, enough patient-reported data that researchers could actually see what works. That real patient knowledge could inform medical research. That we could prove what spoonies already know — we are the experts on our own bodies.

What We Didn't Expect

The biggest barrier to growth isn't technology. It's energy.

When you're designing for chronically ill people, you can't think like a typical growth startup. You can't ask for engagement metrics. You can't push notifications. You can't design for daily active users — because many of our users have days where opening their eyes is the full task.

So we built it differently. We made it possible to log something in 30 seconds. No gamification. No streaks. No social pressure. Just: "Here's what helped me today. Here's what didn't."

But adoption is slower because reaching spoonies requires trust. You have to earn credibility in communities that have been burned by wellness culture, by medical gaslighting, by products built about us instead of with us.

The Real Work

The development isn't the hard part. The hard part is:

Recruitment — Getting 500+ people (our current beta cohort) to tes