fitbuddy
An accountability partner for your training week.

Showing image 1 of 1.
builders behind fitbuddy
core problem they tried solving
A planned workout is easier to postpone when the commitment stays private. People need shared accountability through training groups that makes the week’s plan visible and harder to put off.
the build story
Fitbuddy started from a very human loophole: a workout is easy to postpone when nobody else knows you planned it. The Halos team spent six weeks turning that into private and public training groups, using the group itself as the accountability mechanism.
The team worked in short sprints, tested and iterated, and reached a functional product where people can create or join a group instead of tracking alone. The original domain is gone, but the Render deployment still wakes up and serves the build.
That survival is imperfect. The fallback can take roughly a minute and a half to wake from a cold start, and the build record does not preserve the user feedback that changed the product. Fitbuddy shipped; its domain, speed and learning trail did not hold up equally well.




