Docs
How to use baybay: logging a feed, sharing with a partner, getting back in, and getting your data out. Short pages, because you are busy.
These are short. Each page answers one question and puts the answer in the first line, so you can stop reading there and get on with your day.
Getting started
Your first day
The app is open and it is empty. Here is the whole of what to do on day one, which is less than you think.
Your address
Your household has its own web address. Saving it is the one thing worth doing before anything else.
Put it on your home screen
baybay opens full screen, with no browser in the way, once you add it to your home screen. It takes about fifteen seconds.
Logging a feed
Bottle or breast, an amount if you are counting, and the time already filled in. Two taps for most feeds.
Naps and nights
One tap starts a sleep, one tap ends it, and baybay works out how long it ran so you never type a duration.
When the charts fill in
Your dashboard is nearly empty on day one, and that is expected. Here is what fills it and roughly when.
The daily rhythm
Fixing things
Sharing
Getting back in
Your data
Before you pay
Why it works this way
Why only feeds and sleep
Every other tracker records more than baybay does. Here is the argument for recording less, and what it costs you.
Why there is no Docker image
baybay installs by copying files onto ordinary PHP hosting. What that costs, what it buys, and why it will still install in five years.
One file for your family
Your household is its own database file, not rows in a shared table. That is a privacy decision before it is a technical one.
Something not here?
This set covers the first week and the things people ask most. More pages are coming — twins, editing entries and the rest. If you are stuck on something that is not written down yet, write to us and it will probably become a page.
Installing and running baybay on your own server is a different job with a different document: the README in the repository covers requirements, setup, the command line tool and backups.