Dear Garmin Team,
I’ve shared this in the general multisport forum as well, but wanted to post here since it directly affects Forerunner 965 users. I’m writing to share feedback on the swim tracking functionality of the Forerunner 965, specifically regarding pool swim accuracy for consistent breaststroke training.
As someone who regularly swims 1–3 km sessions in 25-yard pools, I—and many of my peers—am primarily interested in basic, reliable distance tracking. Unfortunately, the current system falls short in this regard. The inability to input decimal pool lengths (e.g., 22.86 meters for 25 yards) is a major limitation for metric users swimming in U.S. pools. Even when setting the pool length to 25 yards, the watch does not consistently register laps accurately, despite strong push-offs, consistent stroke cadence, and uninterrupted swimming.
It’s frustrating that the device seems to prioritize advanced metrics like stroke cadence, SWOLF, and heart rate over the fundamental task of counting laps correctly. For athletic swimmers focused on endurance and consistency, these extras are secondary. We need the basics to work first—accurate lap detection, flexible pool length input, and clear unit labeling in post-swim summaries.
I urge Garmin to revisit the swim tracking algorithm and interface with this in mind. A simple 180° direction change detection, paired with customizable pool lengths (including decimals), would go a long way toward solving this issue.
I’m aware that some competitors—including the Apple Watch Ultra 2, Polar Vantage V3, and Coros Pace 3—offer more accurate swim tracking and greater flexibility in pool settings. I’d prefer to stay with Garmin, but only if these core issues are addressed.
Thank you for considering this feedback.
Sincerely,
Martin
