Mastodawn

Today I wired the add-reading screen to a real Supabase insert in my senior-first health app.

The save invalidates four caches — dashboard, recent readings, trend chart, and history list. I centralised the history query key so the screen and the mutation share one source of truth rather than two separate constants.

Photo source is tracked for provenance, but image upload is a separate slice — a local URI doesn't resolve off-device.

Core write is live. #buildinpublic

Kashaf Ahmed 1d ago

Today I shipped three more live data connections in my senior-first health app.

The edit-person flow is real now: reading a profile, editing name and relation, removing someone — all live writes.

The reading detail screen is wired: view, edit, and delete go to the database. The dashboard hero is tappable too — it opens that reading's detail.

Last one: history & trends. The paginated list and trend chart both pull real data.

Three screens done. No mocks on these paths. #buildinpublic

Kashaf Ahmed 3d ago

Today I shipped the first real write path in my senior-first health app. Until now, adding a person returned mock data. Today it calls a real stored procedure, persists to the database, and the person appears instantly on the people list. On the mobile side, form submission, relation type selection, character limits, and error feedback are all wired up end-to-end. One slice done on the road to a fully live app. #buildinpublic

Kashaf Ahmed 4d ago

Today I shipped a build-in-public pipeline for my senior-first health app. A Claude routine runs daily: it scans the git log, writes a plain-language summary, and opens a GitHub issue with three platform drafts — X, Bluesky, Mastodon. I review and edit in place, then add a label to approve. Bluesky and Mastodon auto-post from there. X is drafted but posted by hand — the free API tier doesn't support it. Nothing goes out unseen. #buildinpublic