Research Note

Strava Garmin Case and Statement Research Note

Strava filed Strava, Inc. v. Garmin Ltd. et al., No. 1:25-cv-03074, in the District of Colorado on September 30, 2025. The complaint asserted three patents and alleged br

Aug 4, 20262 min readBy Dalton Anderson
In this article

Strava Garmin Case and Statement Research Note

Procedural record

Strava filed Strava, Inc. v. Garmin Ltd. et al., No. 1:25-cv-03074, in the District of Colorado on September 30, 2025. The complaint asserted three patents and alleged breach of a 2015 agreement. The complaint requested damages and injunctive relief. Those statements are Strava's allegations and requests.

Strava filed a notice of voluntary dismissal without prejudice on October 21, 2025. The court terminated the case on October 22. The notice gives no reason or settlement term. The public record does not establish infringement, noninfringement, validity, invalidity, breach, victory, capitulation, or a private resolution.

Public communication

Strava Chief Product Officer Matt Salazar published "Setting the record straight about Garmin" through the Strava team account on Reddit. The statement framed Garmin's 2025 attribution policy as a user-experience and user-data problem.

Replies raised Strava's own API and branding requirements, dependence on Garmin-sourced activities, and the practical priority users placed on hardware continuity. These replies establish a visible negative reaction within the thread. They do not prove the view of every Strava user or a quantified subscription effect.

Strava's later developer update acknowledged updated Garmin attribution terms and encouraged implementation review. It does not explain the dismissal.

Publication rule

Use allegation, asserted, requested, filed, dismissed, and terminated precisely. Do not use won, lost, invalid, infringed, settled, forced, or backfired as a procedural conclusion. Keep the case timeline on qualified legal review hold.

Sources

Follow the evidence.

  1. patents.google.com: US9116922patents.google.com
  2. communityhub.strava.com: update regarding garmin attribution best practice 11916communityhub.strava.com
  3. developer.garmin.com: Garmin Developer API Brand Guidelinesdeveloper.garmin.com
  4. storage.courtlistener.com: gov.uscourts.cod.247832.19.0storage.courtlistener.com
  5. docs.stripe.com: upgradesdocs.stripe.com
  6. docs.github.com: breaking changesdocs.github.com
  7. reddit.com: setting the record straight about garminreddit.com
  8. dockets.justia.com: 247832dockets.justia.com
  9. prsa.org: ethicsprsa.org
  10. w3.org: prov ow3.org
  11. developers.strava.com: guidelinesdevelopers.strava.com
  12. patents.google.com: US9778053patents.google.com
  13. ico.org.uk: right to data portabilityico.org.uk
  14. garminrumors.com: Strava vs Garmin Lawsuit Segments 9 30garminrumors.com
  15. developers.strava.com: getting starteddevelopers.strava.com
  16. developers.strava.com: webhooksdevelopers.strava.com
  17. strava.com: apistrava.com
  18. developer.garmin.com: brand guidelinesdeveloper.garmin.com
  19. patents.google.com: US9297651patents.google.com

From this episode

Two useful next steps.

Evergreen · 1 min

What to Do When an API Policy Changes

Preserve the old and new policy, map journeys and data, classify the change, choose adapt, negotiate, replace, narrow, or exit, then communicate clearly.

Episode Story · 1 min

Venture Step E086: Strava, Garmin, and Platform Power

Episode 86 argued that the Strava-Garmin dispute exposed API dependence and weak communication. The lawsuit later ended without a merits ruling.

Return to the episode