Roadmap
Where Arc is going.
Arc is being built around a long-running coaching relationship rather than a finish line. This roadmap shows what got us here, what is available now, and the directions we are working toward next.
-
Station 1 of 5
Foundation
Build the coaching foundation
Before inviting runners into Arc, we focused on the foundations needed for coaching decisions to stay connected rather than becoming isolated answers.
- A shared training arc across Basecamp, Coach, Activity Review, Plan, and Trajectory
- Reviewable changes instead of silently replacing meaningful training decisions
- Activity logging and import foundations
- Product boundaries for safety, transparency, and user control
The goal was to build the system before asking the system to scale.
-
Station 2 of 5
Available in Beta
The current coaching loop
Arc connects the training decision in front of you to the larger picture.
Basecamp, Coach, Activity Review, Plan, and Trajectory work together around today’s decision, the week ahead, and the longer path toward your goal.
Available now
- Plan and review training
- Bring readiness and added context into Basecamp
- Ask Coach questions grounded in your training
- Review completed activities
- Keep individual decisions connected to an active goal
- Log activities manually or import Garmin-compatible CSV/FIT files
-
Station 3 of 5
Building
Easier access. More reliable training data.
The coaching loop becomes more useful when it fits naturally into everyday training.
We are working on the foundations that make Arc easier to access and reduce the work required to keep the training picture current.
Current focus
- A mobile experience designed for the platforms runners already carry
- More reliable connected activity ingestion
- Stronger release, account, and access foundations for a broader Arc Beta
-
Station 4 of 5
Next
One coach that gets better over time
The next major step is making Arc's judgment more coherent, visible, and durable across the product.
We want the athlete to experience Basecamp, Plan, Coach, reviews, and Trajectory as parts of the same coaching relationship—not separate features that happen to share an account.
What that means
Cross-surface coherence
The different parts of Arc should not give conflicting coaching.
Visible learning
You should be able to see what Arc learned and how that changed its behavior.
Continuity across phases
Racing, recovery, maintenance, disruption, and rebuilding should remain part of one coaching story.
Reliable memory boundaries
Useful context should persist appropriately, become stale when it should, and respect correction and removal.
Better judgment over time
Coaching should become more appropriate, not merely more familiar.
-
Station 5 of 5
Exploring
A richer training picture
There are more useful signals around training than any single application can create on its own.
We are exploring ways to bring more of that context into Arc without turning the product into an unrestricted data collection system.
Directions we're exploring
- Additional activity and training-data sources
- Race and event context
- Carefully bounded ways to bring outside context into coaching
- Better ways to visualize the history and direction of a long-running coaching relationship
- Deeper public explanation of Arc's methodology and how coaching judgments are formed