Reliability of Health Connect analysis and a calmer morning flow.
Consolidate feedback from real audiobook and podcast routines.
Only features that measurably improve resuming.
Development
notes.
A snapshot of what I am working on in each project, what is likely to follow, and which ideas are staying on the shelf for now.
ProductNowNextLater
Test native clients, tunnel onboarding, roles, and clear failure states with a small set of home networks.
Publish code and the installation path with the beta.
App-store release after meaningful security and support validation.
Cut a focused product core from the broad demo; prioritise installation, backup, and review.
Signed test builds for macOS and Windows.
Paid distribution only with a tested update and refund path.
Personal vehicle use and small UI improvements.
Clarify build notes and hardware decisions in the repository.
No universal kit planned—forks and ideas are welcome.
Working notes
How I decide what to work on next.
Core flow first
A core flow must be reliable before adjacent features expand.
Include operations
Installation, backup, updates, and failure states belong to the project just as much as the interface.
Release when the path works
Store badges, packages, or prices come only when installation and use are reliable enough.