Why
Chores between housemates fail as a memory problem long before they fail as a fairness problem. What was missing was not effort but a shared record of who agreed to what, visible to everyone at once.
What
My first application built end to end. Groups you create or join by ID, an admin screen that assigns tasks across Monday through Sunday and finalises the week, and a per-person view of the day.
How
Node and Express serve the app; NeDB's promise API stores groups, members, and assignments as file-backed documents. No database server to stand up, which was the right size for a first full-stack build and kept the whole thing deployable as one process.
Make the week a decision
The admin fills Monday through Sunday and finalises it, so the rota gets settled once rather than renegotiated every evening.
Give everyone the smallest view
Once the week is set, a housemate's home screen is just Today. The full schedule exists, but nobody has to read it to know their part.
Onboard with one field
A group is created or joined by ID, because an app for shared chores is worth nothing until the second person is in it.