tatami

Stripped the log form to three taps. The options were a comprehensive session form (positions, duration, session type, reflections, date, felt rating) or a minimal one. I cut everything non-essential and collapsed the date field entirely since 90% of logs happen same-day. The second-order reason: an AI coach is only as good as the data it receives, and a form people skip produces worse training data than a form people actually complete. Completion rate beats field richness.

Gave the AI coach persistent memory across weeks. A stateless weekly summary - regenerating from scratch each time - was the obvious implementation. Instead I stored each week's coaching recommendation in the database and injected the last three as structured context on every subsequent API call. The reason this mattered specifically here: hobbyist users don't train with a coach present, so the sense of continuity - a coach who remembers what they told you last week - is the entire trust mechanism. Without it the feature reads as a novelty. With it, it reads as a relationship.

Excluded submission tracking deliberately. Every comparable app includes it. I removed it entirely from the training room context, keeping it only as a future competition-specific feature. The second-order reason: tracking taps in training changes the social dynamic of the room. Hobbyists train in community gyms where the training environment is the product's real competition; if the app makes the mat feel like a scoreboard, people stop using it to protect their relationships with training partners. The product's job is to support the training room, not to surveil it.