Roadmap
BOB is in private beta. This is the honest version: what works today, what is coming next, and the things we have decided against and will not be adding.
Shipped means live for testers now. Next means committed but not started. Later means we want it and have not scheduled it. Not planned means a decision was made against it, and we say why rather than leaving it vague.
Goals, stories, tasks and sprints as one thread - a ten-year ambition down to a block on Thursday. Kanban, a planning matrix, capacity and burndown.
A scored Top 3, re-ranked overnight on age, deadline and theme. A daily plan, and a nightly re-plan around whatever changed.
Chores, routines and habits. Backlogs for games, books, shows and video. Travel mapping. Themes that budget your week by area of life.
A mobile layout built for it, not a shrunken desktop. An iOS app is in TestFlight during the beta - ask and we will send an invitation.
Everything below works today for people in the beta.
These are the things standing between where we are and letting more people in.
Plan into your real calendar and have BOB work around what is already there. Working in development; the production connection is not, and it is the single biggest thing between here and letting more people in.
Built and running against our account. Needs an end-to-end check with a tester's own Steam account before we call it done.
Committed, not started. These come during the beta.
A new account currently arrives with no sprint, so the planner has nothing to plan and the wizard describes something that is not there yet.
Someone tracking a marathon and someone tracking a business should not both be handed the same empty board.
Show what something does at the point you click it.
Connected, not connected, or broken - in one place rather than scattered through settings.
What you have committed against the hours you actually have, and a warning when those disagree.
Today it is plain text, and its sign-in link expires in an hour while the email says a couple of days.
What goals, stories, sprints and themes mean, and why it is built this way.
Real intentions with no date attached. We would rather say that than imply a timeline we cannot keep.
Training, sleep and recovery feeding your plan. Not built - the data model has a slot for it, nothing fills it yet.
Not built.
TestFlight only while we are in beta.
Not built.
Not built.
Not built.
Partly there - the breakdown works today; the research and automatic scheduling do not.
Not built.
These come up often enough to answer directly. They are decisions, not oversights, and none of them are coming.
The finance side of BOB is fully built - ledger, budgets, pots, categorisation, forecasting. What cannot happen is connecting your Monzo account to it. Monzo's developer API is licensed for personal use only, so an app that connects other people's accounts through it would be breaking their terms. We are not going to do that.
The one honest route is bring-your-own credentials, where you register with Monzo yourself and BOB uses your registration. That is written down as a possibility, not a promise.
Strava caps an application at ten connected athletes without going through their review, and since June 2026 it also requires an active Strava subscription. Ten users is not a feature, so we have not built it into the product.
It runs in our development environment against a single athlete slot and stays there.
Genuinely interesting, entirely unrelated to what BOB is for, and a large amount of work on a platform nothing else in the product touches.
Because you will find them, and it is better you hear it here.
Found something not listed here? Tell us in the chat window, bottom right. We would rather hear it early.
Ask anything about BOB or the beta.