The problem
The daycare app (Brightwheel) is where the teachers record the day. The family app (Baby Tracker) is where we and the grandparents look, and it syncs between our phones. Data only needs to flow one way, but the receiving app has no API, no import and no webhooks.
How it works
Why an emulator
Reverse-engineering the app's private sync protocol would be fragile and could corrupt the family's history. Driving the real app is slower, but it behaves exactly like a manual entry and can't write anything the app wouldn't.
Guardrails
- Every write checks the app is showing the right child first, and refuses if not.
- Each form is read back before saving, and each saved entry is found in the log afterwards. The first mismatch stops the run.
- Naps wait while a sleep is running on any phone, because the app would otherwise edit that sleep instead of adding a new one.
- It polls every 15 minutes between 14:00 and 17:00 only, when the sync matters most.
- Three failed runs in a row and it halts itself and sends a desktop notification. So do an expired login, a stopped emulator, or sync errors in the app.
What it runs on
Pythonadb + uiautomatorAndroid 14 emulatorsystemd user timer
The emulator is a systemd user service that restarts itself, and a timer starts each sync run. It lives on the same home machine as this site.
Status
Running since 10 October 2026. The first day (12 entries) was entered under supervision and checked in the app's own log. On 13 October the 15-minute timer processed a daycare day on its own: eight entries (naps, bottles and diapers) were written, each found in the app's log afterwards, and all of them showed up correctly on a parent's phone. A nap still in progress was held back until it ended, as designed. Entries edited or deleted at the daycare after being copied are not updated at home, and the daycare login has to be refreshed about once a year.