Daily Howdy — Family Connection App for Seniors and Caregivers
What Is This
A multi-tenant family connection app that solves my own problem: a more interesting and informative daily checkin with an aging parent. Seniors play daily word and memory games (Howdy rounds) while caregivers track engagement and receive weekly mood reports.
The app supports web, iOS (Hotwire Native), and Android with real-time push notifications. AI-assisted content generation with admin review keeps the daily rounds fresh.
3,433 commits. 14+ PRDs.
Why This Approach
Senior citizen apps require product taste that most engineers don’t exercise. The UX constraints are different from everything else I build: larger touch targets, simpler flows, minimal cognitive load, no assumptions about technical literacy. The daily game format solves the real problem — “how is Mom doing today?” — without requiring the senior to fill out a form or remember to call.
Hotwire Native was chosen over React Native or Flutter because it lets a single Rails codebase serve web, iOS, and Android with native shell wrappers. For a product with simple interactions but complex backend logic (scheduling, notifications, AI content generation, caregiver reporting), this is the right tradeoff.
Key engineering decisions:
- Multi-tenant account architecture with role-based visibility. Seniors and caregivers see different views of the same data. A senior sees today’s game. A caregiver sees engagement patterns, mood signals, and weekly reports.
- AI-assisted content generation with human review. Claude generates daily round content (word games, memory prompts, conversation starters). An admin review workflow prevents anything confusing or inappropriate from reaching seniors.
- Hotwire Native for web/mobile parity. One codebase, three platforms. Native push notifications and device APIs where needed, shared UI everywhere else.
What Would Break
- Content generation depends on the Claude API. A quality regression in generated content could confuse or frustrate seniors — a population with low tolerance for confusing interfaces.
- The Hotwire Native approach trades native UI polish for development speed. If the app needed complex gestures or heavy offline capabilities, this architecture would need rethinking.
- The multi-tenant model assumes small family groups. Large care networks (facilities, professional caregivers) would need a different permission model.
What I Learned
- Product taste for seniors is undervalued and undertaught. Every default assumption in modern app design (small text, swipe gestures, hamburger menus, onboarding flows) is wrong for this audience.
- AI content generation needs guardrails that are different from typical applications. The failure mode isn’t “unhelpful” — it’s “confusing to someone who can’t troubleshoot.”
- Building for someone you love produces different judgment than building for a market. The quality bar is personal.
Repo: github.com/plentyofsaas/dailyhowdy-app (private)
Live: dailyhowdy.com
Status: Active development.