I've been working on a baby sleep tracker called DreamMorrow. It brings the sleep log and upcoming estimates into one view, so you can see how the day has gone and what might come next. The main screen is called the Dreamline. It puts recorded sleep and wake-ups, the current time, and the next available nap and bedtime estimates on a visual timeline. You can start and stop timers, add a session you missed, correct the history, and share a child profile with another caregiver. I've also been working on the prediction side. There are separate engines for the next sleep opportunity, bedtime, and waking from an active sleep. A locally hosted Ollama service can explain the context behind an estimate in plain language, while the prediction engines handle the timing. I'm building it with .NET/Blazor and PostgreSQL and running it on my home server. I use AI tools for help with implementation and troubleshooting along the way. It works in a browser or as a Home Screen web app, although it needs an internet connection to load and save records. It's still a work in progress. One thing I'm refining is how the estimates and their limitations are explained, especially when there isn't enough useful history. They're intended to help with planning and aren't medical advice or a guarantee of when a child will sleep. The video shows the actual app using synthetic sample data. The times are illustrative examples. https://dreammorrow.com/ I'd be interested in what you think of the Dreamline. Does it make the day easier to follow, or would you rather have a simpler timeline?   submitted by   /u/codtv132 [link]   [comments]