Build a chore tracker and you have built a small economy. Children audit it.
The thing nobody warns you about a chore tracker app is how seriously the users take the arithmetic. Adults let a habit app round things. A nine year old who was promised twenty pence for emptying the dishwasher will tell you, accurately, that it was three times last week and the app only counted two. That is the real requirement, and it is why this is a stricter build than a habit tracker app.
This page is about who gets to say a chore was done, how the points ledger has to behave, what rotation is for, and the part that catches people out: an app aimed at children brings obligations that an app aimed at adults does not.
See who confirms a choreThe short version
Two states for a chore, and a ledger that balances to the penny.
A chore that is ticked and a chore that is agreed are different things, and collapsing them is what turns a family app into a family argument. The child gets the satisfaction of ticking immediately. The points move when a parent agrees it happened.
The ledger underneath has to be a ledger: every entry dated, every adjustment visible, nothing silently recalculated. Not because the amounts are large, but because the user checks. A balance that changes without an entry explaining it destroys the app's credibility faster than any missing feature.
Who gets to say a chore is done
This single decision shapes everything else. Get it wrong in one direction and the app records fiction. Get it wrong in the other and nobody opens it.
Immediate feedback, delayed settlement
The pattern that survives is to let the child mark a chore complete and see that register instantly, while the points stay pending until a parent confirms. Nothing is taken away, and nothing is credited on an assertion. Adults recognise this as approval workflow. Children recognise it as fair, which matters more.
Disputes need somewhere to go
A parent who forgets to confirm for four days has created a backlog of grievance. Show pending items to both sides, and let the child see that something is waiting rather than lost. Most of the emotional weight in these apps sits in that gap.
Try it
Who gets to say a chore is done
This is the whole design. Everything else in a chore app follows from the answer, including whether anybody still uses it in March.
Works until it matters
Fine for tidying a room. The moment points convert into money, a seven year old will find the edge of this in under a week.
The ledger, and why it has to be a real one
Points, stars, pocket money, screen time: whatever the currency, the mechanics are the same and they are accounting mechanics. Earned, spent, adjusted, and a running balance that can be derived from the entries rather than stored on its own.
Storing a balance as a number and updating it is the mistake, and it fails the first time two devices act at once or a parent corrects something. Store the entries and compute the balance. It is barely more work and it means every figure in the app can be explained by pointing at a row.
Adjustments deserve their own entry type rather than being edits to history. If a parent deducts points for something, that is a transaction with a reason, not a quiet reduction. Children spot silent edits, and the trust cost is high.
One more thing worth deciding early: whether points expire. Most families never decide, then discover a child has banked 4,000 points and expects a bicycle.
Rotation, and who always ends up on the bins
Fairness in a household is not equal counts, it is equal unpleasantness, and only the family knows how the two compare. An app cannot rank chores by horribleness, but it can stop the same person drawing the same one indefinitely.
Rotation is worth building as a property of the chore rather than a schedule of assignments, so a chore knows it rotates among a set of people and whose turn is next. That keeps working when somebody is away, which a fixed assignment schedule does not.
Age is the other axis. What a six year old can be asked to do is not what a thirteen year old can, and a shared list that ignores that gets ignored. If you want a record of how things actually went rather than only what was assigned, that is closer to a journal app than a task list, and the daily mechanics of recurrence and rollover are covered properly in a daily task app.
Building for children brings obligations
This is the part people discover late. An app intended for children is treated differently by both the App Store and United States privacy law, and the obligations attach to who the app is for, not to what you intended.
Apple's guidelines for the Kids Category say such apps must not include links out of the app, purchasing opportunities, or other distractions to kids unless reserved for a designated area behind a parental gate. They also say Kids Category apps may not send personally identifiable information or device information to third parties, and should not include third-party analytics or third-party advertising, with only narrow exceptions. Apple adds that once customers expect an app to follow these requirements, it has to keep meeting them in later updates even if you deselect the category.
On the legal side, the COPPA Rule defines a child as an individual under the age of 13, and treats names, addresses, online contact details, phone numbers, persistent identifiers, biometric data and geolocation as personal information. A family chore app collects several of those by its nature. None of this is legal advice, and a private app your own family uses is a different proposition from one published for other people's children, but the line is worth knowing before you publish rather than during review.
What each way of running chores gives a household
| Option | Child can see what is theirs | Ledger explains itself | Rotation | Nobody argues about last week |
|---|---|---|---|---|
| A whiteboard on the fridge | Yes | No | by hand | No |
| A shared note | if they look | No | No | No |
| Spreadsheet a parent maintains | No | Yes | by hand | if it is never overwritten |
| Off-the-shelf chore app | Yes | usually | sometimes | usually |
| A chore app you build | Yes | Yes | Yes | Yes |
Building one around your own household
Chore apps assume a shape of family: two parents, one home, a fixed set of children, pocket money as the reward. Plenty of households are not that. Children between two homes on alternating weeks. A reward that is screen time rather than money. A teenager whose chores are worth more than their younger sibling's and who knows it.
Newly is an AI app builder. You describe the app you want, including how your household actually works, and it builds and ships a real mobile app you own. Plans start at $25 a month, there is no free plan, and iOS builds ship through App Store Connect. It does not process payments, so pocket money stays a number in your app and a conversation at the kitchen table. It is what you use when no chore app matches the arrangement you already have.
One design decision is worth more than the rest: how a child finds out there is something to do. A chore list nobody opens is a whiteboard with extra steps, which is why it is worth reading about the nudge that gets a chore done before you build the list itself.
Questions people ask about chore tracker apps
Both, in two stages. The child marks it complete and sees that register immediately, and a parent confirms before any points move. Letting the child settle their own ledger fails as soon as the points are worth something. Requiring a parent to do all the marking means the child never opens the app.
Describe how chores actually work in your house
Write down who does what, what it is worth and who settles an argument about it, and build the app around that rather than a template family.
Start building