Structuring the Hoxa MVP

The MVP does not need to prove that Hoxa can become a full health platform. It needs to prove that the core planning loop is helpful. A user should be able to define a goal, receive a weekly structure that fits their context, complete workouts across different environments, and feel the plan respond sensibly over time.

That means the first release has to demonstrate coherence more than coverage. Running, strength, mobility, balance, and recovery all belong in scope because they are part of the product thesis. But each one should appear only insofar as it strengthens the main loop: assess, plan, complete, adapt, reflect.

• Goal-based onboarding for beginner to intermediate users, including general fitness and running goals up to half marathon.
• Support for home, gym, and mixed training contexts.
• Weekly planning with clear daily session types and rationale.
• Workout completion logging with enough detail to drive sensible adaptation.
• Recovery-aware adjustments when adherence, fatigue, or schedule changes suggest the plan should shift.
• Lightweight accountability features that reinforce follow-through without turning the product into a social feed.

This set is enough to prove the core loop without asking Hoxa to be everything at once. It allows the product to express a gentler view of training while still giving users real structure. It also creates the right data foundation for future adaptation, because the plan and the completion loop are both present from the start.

Several things are intentionally out of scope for the MVP. Deep device integrations, advanced coaching analytics, generative planning experiments, complex social mechanics, and broad nutrition tracking all make sense as future layers, but they would blur the first release if introduced too early.

The practical reason to wait is focus. The more subtle reason is credibility. If Hoxa makes claims about intelligence before it can demonstrate a reliable core system, the product starts to look like it is borrowing confidence from language rather than earning it through behaviour.

Supporting running goals up to half marathon is important because it expands the product from general fitness into a more concrete outcome. But that support has to be implemented carefully. The goal is not to become a specialist endurance platform in version one. The goal is to help non-elite runners train for a meaningful milestone without neglecting strength, mobility, and recovery.

That framing changes the product decisions. The running plan should not dominate the rest of the week. It should coordinate with it. Hoxa should make the user feel like they are building a durable body that can handle the goal, not just accumulating miles because the plan says so.