Start Here: PainTracker + CrisisCore Build Log (Privacy-First, Offline-First, No Surveillance)
PainTracker is a privacy-first, offline-first pain tracker built for the moments that matter.
No cloud dependency. No surveillance business model. Client-side encryption where it counts.
These posts share the foundations (why) and the build log (how) behind CrisisCore systems.
If you’re living with chronic pain, you deserve tools that don’t trade your safety for “engagement.”
If you’re building healthcare software, you deserve patterns that survive crisis conditions.
Two tracks (pick what you need)
- Foundations: local-first architecture and trust boundaries (offline behavior, storage, validation, exports)
- Build log: crisis-mode UX, testing, and performance under pressure
Start with these 3 posts
- Trauma-Informed React Hooks
- Client-Side Encryption for Healthcare Apps
- Building a Healthcare PWA That Actually Works When It Matters
Foundations (local-first architecture)
- Offline-first without a backend: a local-first PWA architecture you can trust
- Three storage layers in an offline-first health PWA: state cache vs IndexedDB vs encrypted vault
- Service workers that don’t surprise you: deterministic caching for offline-first PWAs
- Zod + defensive parsing in a local-first app: make your offline data trustworthy
- Trauma-informed UX + accessibility as architecture (not polish)
- Exports are a security boundary: the moment local-first becomes shareable
- WorkSafeBC-oriented workflows without overclaims: structured summaries, careful language
Follow the build log
- Start the build log here → https://dev.to/crisiscoresystems/two-people-same-body-a-developers-crisis-architecture-25ko
Support / Try it
- Sponsor → https://paintracker.ca/sponsor
- Try PainTracker → https://paintracker.ca
If you’re building healthcare software, these posts are written for the moments when things go wrong — offline, under stress, and with privacy on the line.
Top comments (0)