DOYOURWORK
Overview
DOYOURWORK started as GyattChores, one family's chore tracker: a single-file React web app that went from cloud-first to local-first with optional Supabase sync. It has since been rebuilt as native apps (SwiftUI for iPhone and iPad, Kotlin for Android) that follow the same scoring rules. Each player builds a daily card of chores up to a 25-minute budget, checks them off, and sends it; an admin, usually a parent behind their own code, approves or rejects each chore, and approved chores feed points, streaks and the weekly leaderboard. Chores nobody does grow bigger and move up the list. Families start from 27 everyday chores or describe their own by typing or dictating, and that list is parsed on the device. On one phone the app never goes online. Add a second phone and every change is encrypted on the device (AES-GCM via CryptoKit) with a key only the family's phones hold, so the server only ever relays scrambled copies. Backups go to a file the family controls, and one tap erases a family from the server.
Stack
Features
- Daily 25-minute chore card: pick your own or let the app suggest one
- Admin approval behind a separate code, so nobody approves their own work
- Points, streaks and a weekly winner on a shared leaderboard
- Skipped chores grow bigger and move up the list until someone does them
- 27 starter chores, or type or dictate your own list; the parsing happens on the device
- No accounts: one phone never goes online; a second phone syncs end-to-end encrypted
- Backup to a file you control, and one-tap erase from the server
- No ads, no tracking, no in-app purchases
Key Technical Challenge
Keeping several phones in agreement on approvals, points and streaks while the server can't read anything it stores: all merging happens on the devices, from end-to-end encrypted changes, with the same scoring rules on iOS and Android so both platforms always reach the same totals.
Lessons Learned
Rewriting a web app as native apps was the moment to rethink the data, not just the UI. Dropping accounts entirely and encrypting before anything leaves the phone made the privacy story simple to say and simple to keep. Rules that look fair on paper don't survive real kids, so escalation for skipped chores and 'nobody approves their own work' came from watching the first version get gamed. And automated UI tests on real devices catch the problems unit tests can't, like a system file panel that stalls.