Building a Ride Analysis Web App with Antigravity and the Strava API

May 16, 2026 · 1:00 PM UTC ·9 min read · 0 reactions · 0 comments · 30 views

#cycling #web development #fitness tracking #strava api #nextjs

TL;DR · WeSearch summary

The article describes the development of a web application called PerfRide, which uses the Strava API to provide advanced cycling analytics and training tools. Built with Antigravity and Next.js, the app offers features like fitness tracking, climb simulation, and pacing optimization for road cyclists. The developer aimed to create a free alternative to Strava's premium analytics with a focus on performance management.

Key facts

▪PerfRide is a cycling performance management web app that integrates with the Strava API.
▪The app provides fitness metrics such as Chronic Training Load (CTL), Acute Training Load (ATL), and Training Stress Balance (TSB).
▪Key features include a climb simulator, pace optimizer, training planner, and dashboard with ride analytics.
▪The app is built using Antigravity and is available on GitHub for public use and contribution.
▪Some features are experimental or partially implemented, such as the weekly workout plan generator.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/gde/building-a-ride-analysis-web-app-with-antigravity-and-the-strava-api-439g
Publication time	Sat, 16 May 2026 13:00:00 +0000
Retrieval time	2026-05-16T13:10:18.577Z
Last seen	2026-05-16T13:10:18.577Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	JKXPr4dz-swv
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3921606) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Akira Kikusato for Google Developer Experts Posted on May 16 • Originally published at zenn.dev Building a Ride Analysis Web App with Antigravity and the Strava API #cycling #nextjs #googlecloud #webdev Introduction I ride bikes a lot these days, and like many cyclists I use Strava to log my rides. Even on the free tier it automatically syncs with smartwatches, cycling computers, and smart trainers, which is plenty for just keeping a record.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments