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.
This page is the front door.
If you are living with chronic pain, you deserve tools that do not trade your safety for engagement.
If you are building health software, you deserve patterns that survive real pressure.
What you will find here
If you want privacy-first, offline health tech to exist without surveillance funding it: sponsor the build → https://paintracker.ca/sponsor
Practical architecture patterns for offline first apps
Security choices explained in plain language
Testing and quality gates that earn trust
Notes from shipping a real product, not a demo
Start with these three
Trauma Informed React Hooks
https://dev.to/crisiscoresystems/trauma-informed-react-hooks-483n
Client Side Encryption for Healthcare Apps
https://dev.to/crisiscoresystems/client-side-encryption-for-healthcare-apps-dhm
Building a Healthcare PWA That Actually Works When It Matters
https://dev.to/crisiscoresystems/building-a-healthcare-pwa-that-actually-works-when-it-matters-md4
Read the Foundations series
https://dev.to/crisiscoresystems/series/34468
Read the CrisisCore Build Log series
https://dev.to/crisiscoresystems/series/34363
Named reading paths
Testing Trauma-Informed Systems
WorkSafeBC Documentation Workflows
AI Agents Under Protective Computing
Trauma-Informed Design
Documentation Integrity / Verifiable Trust
Client-Side Encryption for Health Apps
Protective Computing Doctrine
Start with Protective Computing Is Not Privacy Theater:
https://dev.to/crisiscoresystems/protective-computing-is-not-privacy-theater-2jobThen read Architecting for Vulnerability: Introducing Protective Computing Core v1.0:
https://dev.to/crisiscoresystems/architecting-for-vulnerability-introducing-protective-computing-core-v10-91gThen read Protective Computing Canon v1.0 is now DOI-backed:
https://dev.to/crisiscoresystems/the-overton-framework-is-now-doi-backed-ko7
If you want the trust and verification path
Quality Gates That Earn Trust
https://dev.to/crisiscoresystems/quality-gates-that-earn-trust-checks-you-can-run-not-promises-you-cant-58a3
Maintaining Truthful Docs Over Time
https://dev.to/crisiscoresystems/maintaining-truthful-docs-over-time-how-to-keep-security-claims-honest-2778
Preview Mode First: Agent Plans as PRs
https://dev.to/crisiscoresystems/preview-mode-first-agent-plans-as-prs-plan-diff-invariants-4ikd
Protective Computing Canon v1.0 is now DOI-backed
https://dev.to/crisiscoresystems/the-overton-framework-is-now-doi-backed-ko7
Try it or support it
Try PainTracker
https://paintracker.ca
Star the repo
https://github.com/CrisisCore-Systems/pain-tracker
Sponsor
https://github.com/sponsors/CrisisCore-Systems
One honest note about scope
This is not medical advice.
This is infrastructure. The goal is to help you track reality without giving away control of your data.
If you are building something similar
What is the one rule you use to make sure your offline features never surprise the user
Support this work
- Sponsor the project (primary): https://paintracker.ca/sponsor
- Star the repo (secondary): https://github.com/CrisisCore-Systems/pain-tracker
- Read the full series from the start: (link)
Top comments (0)