
Below is a detailed timeline showing how a once-strong partnership devolved into a legal and public standoff:
2009 – Strava Segments Begin
Strava launched its defining feature, Segments, in 2009. For the first time, runners and cyclists could record GPS data and automatically compete on defined stretches of road or trail. These community leaderboards helped Strava explode in popularity and cemented its reputation as a social platform for athletes.
However, Strava did not file for a patent until 2011—two years after the feature went public. Under U.S. patent statute 35 U.S.C. §102(b), inventors generally have only one year after public disclosure to file, making it difficult for Strava to claim novelty. That detail may prove important now, as Garmin argues the patents should never have been granted.
2012 – The True Birth of Heat Maps
Before either company filed for patents, smaller developers were already experimenting with overlaying GPS activity data on maps to visualize where people ran or rode most frequently. The first working implementation appears to have come from a third-party tool called RaceShape, created by engineer Paul Mach using Strava’s public API. RaceShape introduced athlete-specific heat maps in mid-2012 — months before Garmin’s official release.
In case you missed it, @raceshape now features a heatmap of rides http://t.co/Xcd6KjCz
— Paul Mach (@paulmach) July 28, 2012
RaceShape continued to expand into early 2013 with more features like athlete-specific updates and sharing.
After a bit of a break we have a new feature, sharable, updatable, athlete specific heatmaps http://t.co/mMdx3eMt
— Race Shape (@raceshape) January 16, 2013
Online records indicate Strava later acquired RaceShape through the hiring of its founding engineer Paul Mach, who joined Strava in October 2012. Mach later confirmed the acquisition in 2017:
I’m sorry for the issues, but sold raceshape to strava 5 years ago and left 1 year ago. I no longer have access.
— Paul Mach (@paulmach) February 10, 2017
Only months after Mach’s hire, Garmin became the first major brand to formalize the concept. It added heat maps to Garmin Connect in March 2013, showing popular routes in major U.S. cities, helping users discover safe or scenic paths and demonstrating Garmin’s growing interest in social data aggregation. Heatmaps were not yet included directly in the Strava application.

Screenshot of Garmin heat maps shortly after launch in 2013. Source: cape-hike.co.za
Strava itself didn’t introduce its own heatmap feature until September 2013, when it launched Personal Heatmaps showing an individual athlete’s activity routes. This timeline suggests RaceShape’s third-party heat maps appeared first (2012), followed by Garmin’s own implementation in early 2013, and finally Strava’s first heatmaps later that same year.
2014 – Patents Filed After the Fact
In December 2014, more than a year after Garmin’s heat map release, Strava filed U.S. patents covering heatmap generation and routing — U.S. 9,297,651 and U.S. 9,778,053 — titled “Generating User Preference Activity Maps.” The filings describe “collecting a plurality of user activities recorded by GPS devices and determining a map based on aggregate user data.” Both were approved in 2016 and 2017.
By then, however, multiple examples of similar systems already existed, including Garmin’s, raising questions about their validity as prior art. The focus of these patents lies not in displaying heat maps, but in using heat maps to generate or suggest routes based on collective user data automatically.
2014–2015 – Garmin Segments and Cooperation
In 2014, Garmin introduced Garmin Segments, a feature likely inspired by Strava’s popular segment system. It allowed users to create custom time-trial sections and leaderboards within Garmin Connect. Unlike Strava at the time, Garmin’s version enabled athletes to view and race segments in real-time during their activities, although it lacked Strava’s robust social ecosystem.
To close that gap, Garmin and Strava signed a Master Cooperation Agreement (MCA) in April 2015, paving the way for Strava Live Segments on the Garmin Edge 520 that July. The partnership enabled starred Strava segments to sync automatically to Garmin devices, allowing users to compete against personal records and leaderboards directly on their screens. The agreement also likely stipulated that Garmin would halt development of their own segments feature.

Garmin Edge 520 showcasing Strava Live Segments (July 2015 launch).
2015–2024 – A Decade of Growth and Mutual Dependence
Following the 2015 integration, the Garmin–Strava partnership flourished. Over the next decade, Garmin became one of Strava’s, if not the largest, source of activity uploads—particularly among paying Strava Premium subscribers, who relied on the Garmin devices.
As Garmin’s watch and bike computer lineup expanded through the Forerunner, Fenix, and Edge series, Strava benefited from a steady influx of high-quality GPS, heart rate, and power data. For many athletes, Garmin devices have become the default way to log workouts, while Strava serves as the social and analytical hub.
By 2024, Strava’s own Year in Sport reports consistently listed Garmin as the dominant connected ecosystem. Among cyclists, Garmin Edge devices held the top two spots globally. And while the Apple watch holds the #1 and #2 spot, the data is a bit skewed because Strava aggregates all Apple Watch models, but does not do the same for Garmin.

Strava’s 2024 Year in Sport report lists Garmin as the leading connected ecosystem.
Garmin, for its part, leveraged the relationship to enhance user engagement. The automatic syncing to Strava made Garmin devices feel instantly connected to a broader community, while Strava’s Live Segments and social features provided value that Garmin’s own platform struggled to replicate.
November 2024 – Strava API Terms Restrict Developers
In late 2024, Strava introduced new API terms that restrict third-party use of activity data. While not directly related to the suit, the data changes are relevant to the broader context of how each company allows their data to be used by third parties.
Key rules from the November 2024 update:
- Third-party apps can no longer display Strava user activity data publicly or to other users — only the individual athlete can see their connected Strava data.
- Developers are explicitly prohibited from using Strava data for AI or machine learning purposes, even for aggregated or anonymized analysis.
- Apps may not process or analyze Strava data to generate insights, summaries, or analytics — including comparisons, leaderboards, or heat maps.
- Strava added language asking apps to avoid replicating its “distinctive look and feel” or core functionality such as leaderboards and social feeds.
Several partners, including Trailforks, lost access and were forced to delete user data. Garmin objected publicly, noting that “data created on a Garmin device originates from the user, not Strava.”
May 2025 – Garmin Trails+ Launch
Garmin launched Trails+ in May 2025, expanding its routing, trail discovery, and popularity layers under the Connect Plus umbrella. The feature aggregates user activity data to highlight frequently traveled routes, a capability long associated with Strava’s own heatmaps and popularity routing tools.
By providing curated paths and dynamic route suggestions, Trails+ signaled Garmin’s growing independence from Strava’s ecosystem and its intent to offer a fully self-contained mapping and routing experience. The overlap between Trails+ and Strava’s features very possibly became a point of friction between the two companies.
June 2025 – Garmin Updates API Brand Guidelines
In June 2025, Garmin published new Developer Brand Guidelines. These did not require the Garmin logo — only simple text attribution such as “Data sourced from Garmin device.”
From Garmin’s 2025 API Brand Guidelines:
- Visible notice: “Data sourced from Garmin device.”
- Logo optional unless co-marketing.
- Attribution must appear where Garmin data is visualized.
June–July 2025 – Private Warnings and Escalation
- June 30: Strava warns Garmin of patent infringement on heat maps and segments.
- July 1: Garmin API policy takes effect; Strava calls it “blatant advertising.”
- July 25: Strava issues second notice, prepares lawsuit.
Late September 2025 – Strava Files Suit
Strava’s lawsuit accuses Garmin of infringing two patents and breaching the 2015 MCA. Analysts believe this move was a direct response to Garmin’s new attribution rules—using old patents as leverage.
- Patent Infringement: Strava cites its Segments patent (U.S. 9,116,922, filed 2011, granted 2015) and Heatmap patents (U.S. 9,297,651 and 9,778,053, filed 2014–2016).
- Agreement Violation: Garmin allegedly breached the 2015 Master Cooperation Agreement (MCA).
Strava states that it warned Garmin in June and July 2025, and that Garmin “willfully” continued its behavior. They seek an injunction to halt device sales and damages.
October 2025 – Public Reaction and Fallout
The lawsuit was first reported by DC Rainmaker and quickly spread through tech and fitness communities. Strava later posted on Reddit claiming it was defending user data, but the lawsuit and Reddit campaign were widely viewed as retaliation for Garmin’s API policy.
Garmin’s new API attribution rules require that data sources (like Garmin Connect) be clearly credited when shown in third-party apps. Strava pushed back, calling this “blatant advertising.” However, many observers noted that Strava’s stance appeared inconsistent, since its own 2024 API terms restrict developers far more tightly — including limits on analytics, AI use, and public data display.
Setting the record straight about Garmin by u/strava-team in Strava
Strava’s Chief Product Officer Matt Salazar posted this in r/Strava.
The backlash was immediate. Within hours of Strava’s Reddit post defending the lawsuit as a matter of “data integrity,” hundreds of athletes criticized the company’s position as hypocritical and self-defeating.
- “Pot calling the kettle black.” Users noted that Strava enforces equally strict—or stricter—developer rules on its own API partners.
- “I’ll choose Garmin.” Many paying users said Strava’s core value depends entirely on seamless Garmin integration.
- “Literally just cite Garmin like Google Earth.” Commenters mocked Strava’s objection to attribution as overly defensive and tone-deaf.
Implications for Both Companies
The potential outcomes of this case carry major consequences for both brands—and for millions of users who rely on their integration.
If Garmin loses, it may be forced to remove or redesign routing and segment features across its lineup. That would disrupt user experiences and complicate data sharing between platforms. However, many believe this is unlikely given the clear examples of prior art and the age of the patents.
If Garmin wins, the result could be far more damaging for Strava. Invalidated patents would weaken its intellectual property portfolio and could lower its valuation ahead of any public offering. More immediately, Garmin could decide to restrict Strava API access or end automatic activity uploads, cutting off millions of Strava users from the devices that generate the majority of their data.
The broader implication is the collapse of a once-symbiotic relationship. For nearly a decade, Garmin supplied the data and hardware, while Strava provided the social network and visibility. This lawsuit signals the breakdown of that arrangement and suggests that Garmin could focus on building a fully independent ecosystem through Connect, Connect IQ, and Trails+ all while Strava risks isolating itself from the hardware partners that made it successful.
Summary of Key Dates
| Year | Event | Feature / Issue | Company |
|---|---|---|---|
| 2009 | Segments launched | Community leaderboards | Strava |
| Jul 2012 | RaceShape heat maps launch | Third-party API visualization | Independent |
| Mar 2013 | Garmin heat maps | Popularity routing | Garmin |
| Sep 2013 | Strava Personal Heatmaps | Individual activity visualization | Strava |
| Dec 2014 | Heat map patents filed | U.S. 9,297,651 & 9,778,053 | Strava |
| Nov 2024 | API restrictions | “Powered by Strava” requirement | Strava |
| Jun 2025 | API attribution guidelines | “Data sourced from Garmin device” | Garmin |
| Jul 2025 | Patent lawsuit (retaliation) | Segments & heat maps | Strava |
| Oct 2025 | Reddit backlash | API dispute & retaliation campaign | Strava |
Sources: DC Rainmaker, U.S. Patent Office filings, Garmin Developer Brand Guidelines (Jun 2025), Strava API documentation (Nov 2024), r/Strava, RaceShape archives, various X posts, Garmin, public company statements, and other sources listed throughout this timeline.






I can’t believe Strava is arguing with Garmin so fiercely without a legitimate reason. Or why would they deliberately shoot themselves in the foot like that? Megalomania/driving up the price…? Perhaps they have a restrictive contract with Garmin (the details of which we don’t know) and are hoping that Garmin will back down because of the lawsuit and they can renegotiate?