Why Pain Tracker
Why Pain Tracker
Pain Tracker was built to keep pain records private, reliable offline, and useful in real care workflows without requiring accounts or centralized data collection.
The Problem
Many health apps break down in the moments when people need them most.
- They depend on connectivity — which can be unreliable in hospitals, rural areas, transit, or crisis conditions.
- They collect unnecessary data — creating privacy risk and placing sensitive information in systems people do not control.
- They require accounts — adding friction, credentials, and another platform holding health-related information.
- They add pressure — through streaks, scores, or behavior patterns that can feel judgmental instead of supportive.
- They restrict basic use — by putting exports, reports, or useful workflows behind paywalls.
Pain Tracker was built as a response to those patterns.
The Approach
Pain Tracker is designed around privacy, local control, and practical use under unstable conditions.
Works Offline
- Track pain without depending on a live connection.
- Designed around local-first behavior.
- Built to remain useful when connectivity is limited or unavailable.
No Account Required
- No signup required to begin using the app.
- Fewer barriers between opening the tool and recording what matters.
- Less unnecessary account-based data collection.
Local-First Data Handling
- Records stay on the device unless the user explicitly exports them.
- Designed to reduce centralized collection and unnecessary exposure.
- Focused on user control over sensitive information.
No Judgment-Oriented Design
- No streak pressure.
- No compliance framing.
- No guilt-driven interaction patterns.
- The goal is support, not behavioral scoring.
Open and Accessible
- Open source: github.com/CrisisCore-Systems/pain-tracker
- Built to be usable without locking basic value behind subscriptions.
- Export and reporting workflows are treated as core functionality, not premium extras.
WorkSafeBC Support
- Includes documentation-oriented workflows for WorkSafeBC use cases.
- Structured logs can support claim-related recordkeeping.
- Designed to reduce repetitive manual effort.
Who It Is For
People with Chronic Pain
People who need a private, practical way to track flares, triggers, medications, symptoms, and functional impact.
Workers Managing Documentation
People who need structured records that can support WorkSafeBC-related workflows and reporting.
People Failed by Existing Health Tools
People who need a tool that is more private, lower-friction, and more reliable under difficult conditions.
Builders and Contributors
Developers who want to study or improve a privacy-first, offline-first health tool in the open.
How It Works
- Open the app — no signup required.
- Track what matters — pain, location, triggers, medications, notes, and patterns.
- Generate usable records — for appointments, personal review, or documentation workflows.
- Keep control of your data — with local-first handling and explicit export decisions.
Why It Was Built This Way
Pain Tracker was built from lived experience of instability, pain, and system failure.
That matters because product decisions change when reliability is not theoretical.
- Offline-first reflects the reality that connectivity is not always available.
- No account requirement reduces friction and unnecessary exposure.
- Local-first design supports user control over sensitive records.
- Non-judgmental interaction reflects the need for support without added shame or pressure.
Pain Tracker was built to be useful when conditions are not ideal.