Today I shipped the invite accept/deny flow — the last piece of the sharing loop. You open a /join/ link, preview who invited you and to what, then Accept or Deny. Works logged-out too: sign in first, and the flow picks up automatically. #buildinpublic
Today I closed a small loop: the reading detail screen now shows the actual stored photo instead of a placeholder. The photo capture flow is now fully visible end to end — take it, save it, review it. #buildinpublic
I shipped two back-to-back features: a Claude Vision edge function that pre-fills the reading form from a photo (falls back to manual if unclear), and the Manage Access screen — view who has access, edit roles, revoke invites. #buildinpublic
Today I shipped the invite screen for my senior-first health app. Two tabs: send a targeted email invite with a role, or create a multi-use sharing link. After sending, the app gives you a profile link to share any way you like. #buildinpublic
Today I shipped the account edit screen for my senior-first health app. You can now tap Settings → your name to edit it. Avatar and email are read-only — no surprises. The whole thing uses a discard guard so you don't lose unsaved changes accidentally. #buildinpublic
Today I shipped settings persistence and a theme toggle in my senior-first health app. Your default person and Light/Dark/System preference now save across sessions. Also wired account deletion — one tap, clean removal. #buildinpublic
Today I finished wiring every reading screen to real data in my senior-first health app. The edit screen now loads the actual record — and I moved delete out to the detail view, keeping edit focused. #buildinpublic
Today I wired the add-reading screen in my senior-first health app to a real database insert. The save refreshes four surfaces at once — dashboard, recent readings, trends, and history all stay in sync. #buildinpublic
Today I shipped three more real data connections in my senior-first health app. Edit person, reading detail, and the full history & trends screen all talk to the database now. No more mocks on those paths. #buildinpublic
@pcshipp it's true, i tried to do same because everyone said to do so... but it is very demotivating experience.. i'll rather be delusional than demotivated.
Today I shipped the first real write in my senior-first health app. Adding a person now saves to the database for real — name, relation, and a few optional details. No more mocks on this path. #buildinpublic
Today I shipped a small build-in-public pipeline. Claude reads the day's git activity, drafts a post, and opens a GitHub issue for review. Once I approve it, Bluesky and Mastodon auto-post. X is manual — the free API tier doesn't allow it. #buildinpublic