Writing useful feedback for a golf app
Good product feedback describes a task and what happened. A structured note can help an app team understand a golfer's needs without assuming a feature already exists.
Work through the checklist
Choose one task, such as finding an event or reviewing a score. Describe what you expected and the steps you took in ordinary language.
Record the result, device type and any non-sensitive error message. Remove names, location details and other players' information from screenshots.
Explain why the issue matters and suggest an outcome rather than insisting on a particular design. Separate a bug report from a new-feature request.
A useful question
What if the app is still being developed?
Describe the need or workflow you want supported. An announcement about development is not evidence that a feature is available or that a launch date is fixed.