DEV Community

Cover image for Start Here: PainTracker and the CrisisCore Build Log
CrisisCore-Systems
CrisisCore-Systems

Posted on • Edited on • Originally published at dev.to

Start Here: PainTracker and the CrisisCore Build Log

If you are new here, this page is the fastest route to the right post for your goal. Pick one path below and skip everything else for now.

Summary The fastest reading path into PainTracker posts by goal with direct links into key architecture and workflow topics.

Start Here: PainTracker and the CrisisCore Build Log

PainTracker is a privacy first local first PWA for chronic pain journaling, built with React and TypeScript for bad internet days and hard days.
Local only data by default. 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

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

Try it or support it

Try PainTracker
https://paintracker.ca

Star the repo
https://github.com/CrisisCore-Systems/pain-tracker

Sponsor
https://paintracker.ca/sponsor

Whitepaper
https://paintracker.ca/whitepaper

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

Top comments (0)