PuttLab AI

I’m exploring a golf-practice concept that turns session observations into clearer feedback and useful next steps.

I use this project story to document the thinking, decisions, and current state of the work. The status above distinguishes an active build or working concept from a finished product.

Practice data is only valuable when a player can understand what changed and what to work on next.

• Clarify who the project is for and what useful progress would look like.
• Define the essential information and system states.
• Keep the experience understandable across common device sizes.
• Document assumptions that still need real-world validation.

• I’m defining the product idea, feedback workflow, and prototype direction.

I’m starting with the coaching decision, defining the minimum useful inputs, and presenting recommendations with visible context rather than opaque certainty.

1. Understand the current state
2. Organize the required behavior
3. Build and review the working concept
4. Document decisions and open questions

• Session capture
• Pattern summaries
• Practice recommendations
• Progress review

• My testing plan covers critical paths and boundary conditions.
• I check responsive behavior, accessibility, and content clarity.
• Real-world system assumptions still need validation before deployment.

This is a working concept. The feedback workflow is taking shape, while model accuracy and real practice results still need validation.

• I get better results when I define the practical need before adding complexity.
• Visible system states and assumptions make the work easier to evaluate.
• Feedback belongs throughout the project, not only at the end.

• Define a small, testable session-data model.
• Prototype the feedback and recommendation views.
• Evaluate whether the concept is genuinely useful during practice.