Dayplan is starting to come together

Dayplan started with a familiar problem: my calendar knew where I needed to be, my task list knew what I owed, and my food log lived somewhere else. I wanted them close enough to be useful together.

The calendar now has Time Blocks that hold actual task lists. I can move tasks between them, reorder the work, and see when the estimates exceed the time I’ve reserved. Appointments stay separate as Events, with busy or free time.

The assistant can work across those pieces. A request can become a proposed set of tasks, blocks and Events—or split a block around an appointment. I review the changes before applying them, and can undo the plan as a group.

Completed tasks can also contribute to matching habits. Clear count-based matches get credited once; uncertain matches need review. A scheduled hour doesn’t automatically become an hour of exercise.

Food is the newest part. A meal photo becomes a draft with ingredients and estimated portions. I can correct the food, adjust the amount, or answer a question and request a revised estimate before saving. A compressed photo can stay attached to a draft or saved meal. I can turn off saving new photos or remove a photo from a meal.

The estimates still need that review. In a small test of twelve meal photos, only five calorie estimates landed within 20% of the reference. The review screen gives me a way to correct the result; it doesn’t make the initial guess more accurate. The full numbers — and why the design assumes the guess is wrong — are in The Review Is the Feature.

Behind the interface, changes have a readable History, and scheduled backups are checked by restoring them into a separate test instance. Those details matter when the app starts holding more of my day.

This version is still running on DEV. Real-phone testing, browser authentication and HTTPS, and off-server recovery remain ahead before I move it to production.