General information, not medical advice. Your midwife, health visitor or paediatrician knows your baby. This page is not for babies born early, babies who are not gaining weight, babies with a medical condition, or babies on a specialist formula: follow your care team’s plan.
How does a shared baby feeding tracker work in Milkies?
It depends on two things: that you pair the phones in person, and that the app is open on each phone now and then. You pair them once, in Settings, under “Log together”. From then on, whoever gives the bottle, changes the diaper or gives a dose logs it; the other phone shows it within about 15 to 20 seconds while both phones have Milkies open, with a note like “1 update from Sam’s phone”. Today’s total, the time since the last feed and the usual gap between feeds then read the same on both.
What does a shared night look like?
Here is an example night with two parents, each logging on their own phone. By morning, both phones show all of it. Milkies doesn’t label entries by phone; the “Logged on” column is only here to show who was up. The app logs mL and kg only; the oz column is here for reading.
| Time | Logged on | What | mL | oz |
|---|---|---|---|---|
| 22:40 | Alex’s phone | Bottle, formula | 90 mL | 3.0 oz |
| 22:55 | Alex’s phone | Diaper | – | – |
| 01:55 | Sam’s phone | Bottle, breast milk | 120 mL | 4.1 oz |
| 02:30 | Sam’s phone | Pumping session | 150 mL | 5.1 oz |
| 05:10 | Alex’s phone | Bottle, formula | 100 mL | 3.4 oz |
| Morning | Added up by you | Fed overnight | 310 mL | 10.5 oz |
Milkies itself shows a total per day, not per night: in the morning, today’s total is 220 mL, and the 22:40 bottle counts toward the day before.
For how much babies tend to drink, see how much formula by weight; for how often, see how often a newborn eats.
How do you pair two phones?
- Invite. On the phone whose logs you want to keep, open Settings, find “Log together” and tap Invite. Give the phone a name, such as “Alex’s phone”, and it shows a QR code. The code works once and expires in 10 minutes.
- Join. On the other phone, open the same card, tap Join, name that phone and scan the code. Do this with both phones in front of you. There is no link to send. Scan in person, and don’t share a photo of the code.
- Check four emoji. Both phones work out four emoji from the key they just agreed. If the two screens show exactly the same four, the inviting phone taps “They match — pair”. If they don’t match, you cancel and nothing is paired.
If two phones answer the same invite, Milkies refuses it and asks you to make a new one, because someone else saw the code.
What happens to the logs on the joining phone?
They are erased. The inviting phone’s log becomes the shared log, and the first sync copies it onto the joining phone. Milkies does not merge two separate histories at pairing time.
If the joining phone already has logs, it warns you first and offers three ways out: back up first, then join; invite from this phone instead, so its logs are the ones kept; or join anyway. Nothing changes on the joining phone until the inviting phone confirms the emoji. So if one of you has been logging for weeks, let that phone invite.
When do the two phones sync?
Only while Milkies is open. With the app on screen, it checks for the other phone’s changes every 15 seconds and sends your own a couple of seconds after you log. When you leave the app, sync stops. There are no push notifications and nothing runs in the background.
- Offline is fine. You can log without a connection. Changes go out the next time the app is open and online, and the card says “Offline — will retry” in the meantime.
- The relay holds messages for a while. Changes pass through ntfy.sh; the ntfy server keeps messages for 12 hours by default. Milkies resends anything the other phone hasn’t confirmed, so a change still gets there, even if it takes both phones being opened again.
- You can see how fresh it is. The card reads “Up to date · just now” or “Last heard 20 min ago”, and has a Sync now button.
Who can read a shared log?
Only the two paired phones. Pairing uses an X25519 key exchange, keys come from HKDF-SHA256, and every message is sealed with XChaCha20-Poly1305 from a well-known crypto library. The relay only sees sealed text on random-looking topic names derived from the pairing secrets, plus message timing and sizes. The pair key lives in the phone’s secure storage (the Android Keystore, or the iOS keychain set to this device only), not in the app’s database.
To be precise about the relay: the ntfy FAQ says its logs contain topic names and IP addresses, and that ntfy.sh forwards messages to Firebase Cloud Messaging. Milkies sends each message with the “Firebase: no” header, which asks ntfy.sh not to forward it. Either way, what passes through can’t be opened without the pair key. There is no Milkies account and no Milkies server holding your data.
What is shared, and what isn’t?
Shared: bottle feeds (breast milk or formula), pumping sessions, diapers, medicine and vitamin doses with their free-text name and amount, and weights. Edits and deletions sync too. Because weights sync, the daily goal worked out from the latest weight is the same on both phones.
Not shared: each phone’s language, theme and tips. Pairing is for exactly two phones and one log, so a third phone, such as a grandparent’s, can’t join the same pair.
What happens if you unpair or change phones?
Unpairing stops sync and keeps every log on both phones. Milkies also tries to tell the other phone, so it stops too. To move to a new phone, the phone that stays taps Unpair first, then Invite, and the new phone joins: it gets the full log from the phone that invites. If the old phone is lost, its message never arrives, so unpair the remaining phone by hand.
While paired, restoring a backup only offers Merge, because Replace would wipe one phone and leave the two out of step. Deleting all data unpairs first, and the other phone keeps its copy. A backup file and a CSV export are in Settings for keeping a copy of your own.
Why does a shared log help with night feeds?
The NHS says there is no need for a feeding schedule, and that babies vary in how often they want to feed. Without a fixed timetable, the question at 3am is often “when did she last eat, and how much?” With a shared log, the parent who is up can check the time since the last feed without waking the other. If you take turns at night, how to split night feeds covers the planning side. A shared record is also easier to show your midwife or doctor than two people’s memories.
What Milkies doesn’t do
Sync runs only while the app is open, never in the background. It pairs exactly two phones and tracks one baby. It doesn’t merge two existing logs when you pair, so the joining phone’s logs are replaced. It has no reminders, no sleep tracking, no nursing timer or breast side, no wet or dirty diaper split, no oz or lb entry, and no percentile charts.
Milkies puts every feed either of you logs on both phones, so the one who is up at 3am can see what happened at midnight. Free, no account, no ads.
Get MilkiesSources
- NHS Start for Life: Feeding on demand (no review date shown)
- ntfy documentation: Configuring the ntfy server, Message cache (default cache duration 12 hours)
- ntfy documentation: FAQ (no date shown)
- ntfy documentation: Publishing, Disable Firebase (no date shown)
- American Academy of Pediatrics, HealthyChildren.org: How to Tell if Baby is Getting Enough Milk (updated 13 January 2025)
- NHS: Dehydration (reviewed 1 May 2026)
Sources checked as of .