Search for a command to run...
Series
A 12-part series on building a privacy-first, accessibility-first, offline-first health PWA.
When something goes wrong in a health tool, the user can lose trust and momentum. Your job is to fix problems without turning the app into surveillance. Shipping a health-adjacent tool is different from shipping a hobby app. Reliability is part of ca...
It’s easy to ship a screen that “looks fine” and still blocks someone from completing the task. Testing is how you catch that early, before it becomes a habit. Accessibility isn’t a checklist you complete once. It’s a feedback loop: you test, you lea...
Privacy threats aren’t abstract. They look like a shared device, a curious coworker, a browser extension with too much access, or an export sent to the wrong place. Threat modeling doesn’t require a security team. It requires honesty. For small teams...
Before someone trusts you with a log entry, they need to trust something simpler: that the app will open, behave predictably, and not get in their way. If Parts 1–6 are about trust, Part 7 is about trust signals. People don’t evaluate a health tool t...
Reliable tools don’t require ideal conditions. They work in basements, parking lots, clinic hallways, and anywhere a person might be trying to get through their day. Offline-first is a promise: “This tool works when your life is unstable.” For a heal...
After you ship, the most valuable lessons are rarely the technical ones. They’re the ones about what users actually need when life is hard. A retrospective is only useful if it names the tradeoffs. If you’re building anything “health-adjacent,” you w...
