- Project
Famtastic
[status: coming soon]
- Role
- Designer and developer
- Stack
- Next.js, React, TypeScript, Mantine, Clerk, Neon, Drizzle, Claude API
- Year
- 2026
- What I owned
- Design and build, including the data-access layer that both the dashboard and the chat are forced to use.
- What I shipped
- A household dashboard in daily use. Roles, permission-aware chat, meals, chores, shopping, illness tracking, and parent-gated budgets. Screenshots will follow.
Overview
A household dashboard the family actually uses. Meals, chores, shopping, money, and a chat that answers from real data without crossing permission lines: parents see the household; children see what is theirs.
The problem
One place for meals, chores, money, and the questions people actually ask, with different views for parents and children. An earlier standalone meal-planning app of the same name is paused.
The process
The hard problem is not the cards on the home screen. It is one app with different views, including the assistant. Every read and write goes through a permission-aware data layer. The model cannot ask for another member's mortgage because the tools never take a member id: the server injects the signed-in person.
Kids must never receive household finance through the assistant.
Measuring success
Daily use in one household is the current bar. There is no public product yet.
Outcomes
Roles, permission-aware chat, meals, chores, shopping, illness tracking, and parent-gated budgets. Screenshots will follow. There is no public link yet.