When should you use it?
- No app tracks the mix of readings you need
- You want data to stay on your phone
- You can describe what you want but not code it
Not for: Medical devices or dosing decisions; Sharing data with clinicians without an export check
What do you need, and what do you get?
You need
- List of readings to track
- Target ranges from your care team
- A phone
You get
- Installable offline web app
- Daily log
- Export for appointments
How does it work, step by step?
- List what you trackWrite each reading, its unit and how often you record it.
- Start smallAsk for a single-screen app that logs one reading and saves it on the device.
- Add readings one at a timeTest each new field on your phone before asking for the next.
- Add an exportHave it create a printable or CSV summary to take to appointments.
- Back upExport regularly; local-only data disappears with the phone.
The prompt
Our own prompt, inspired by u/TheVPAline on r/ClaudeAI and written to work in Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Build a single-file progressive web app I can install on my phone. It must work offline, store data only on the device, and need no login. Screen 1: log {first_reading} with date and time. Show the last 7 days as a list. Add a button to export all data as CSV. Keep the code simple and explain how to install it on {phone_type}.
Inspired by u/TheVPAline on r/ClaudeAI: 73 years old, no coding experience, cardiac patient — I built a real health app with Claude after a hospitalization. Here's what happened.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Local storage can be cleared by the browser; keep exports.
- Ranges and alerts should come from your care team, not the AI.
Our take
The motivation is the point: he could not find a tracker that kept everything on the phone with no account, so they made one. Building by conversation works best in small increments tested on your own device, which is how the app reached many versions. Add regular exports so data survives a lost phone, and leave every target range to the care team. Ask for plain code you can read, not a large framework. Share open source carefully without personal data in the repo. Start by listing each reading, its unit and how often you record it, then ask for a single-screen app that logs one reading and saves it on the device. Add fields one at a time and test each on your phone before the next. Browsers can clear local storage, so keep regular exports, including a printable or CSV summary for appointments. Alerts and target ranges should come from your care team, never the AI.
Where the time goes back: Several separate logs and notebooks become one app you open each morning.
FAQ
Do I need to code?
Is my data private?
Source and credit
Inspired by u/TheVPAline on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- 73 years old, no coding experience, cardiac patient — I built a real health app with Claude after a hospitalization. Here's what happened.
- Creator
- u/TheVPAline on r/ClaudeAI
- Published on
- Original date
- Mar 24, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.