Feature
Strava Integration
Strava Integration lets Diorama read supported workouts from Strava and use them as context for recovery, trends, insights, and workout detail. Strava remains the place many athletes record, review, and share training. Diorama uses that record privately to understand what the effort may mean for the rest of the day, the next morning, and the patterns that build up over time.
You already use Strava to capture the effort: the run, the ride, the swim, the route, the device, the pace, and the training history. Diorama adds the surrounding context that explains what happened next. A hard ride might look great in Strava and still explain poor sleep that night. A moderate swim might be the thing that steadies mood after a stressful day. A Garmin workout might arrive in Apple Health as a thin summary while Strava keeps the device and sport detail Diorama needs to classify it correctly. The integration connects those dots without turning your workout history into duplicate entries.
Why it matters
Many users already have their best workout data in Strava because Garmin, Wahoo, Polar, Suunto, bike computers, treadmills, cycling apps, and swim tools send data there first. Apple Health can receive the same workout with fewer details, delayed updates, or aggregate-only summaries. A direct Strava connection gives Diorama another trusted path to recover the missing context without asking users to log the workout manually.
How Diorama uses this
Diorama treats Strava as an enrichment source, not a duplicate workout source. If Apple Health and Strava describe the same workout, Diorama should show one workout and attach the better available fields from Strava where HealthKit is missing detail. Examples include source device name, sport type, distance, elapsed duration, power, cadence, route or stream availability, and lap or split metadata when Strava exposes it. The practical value is simple: Strava shows what you did. Diorama helps explain how that effort fits with sleep, recovery, habits, mood, soreness, and the next decision.
Product position
Strava is the athlete network and performance log. Diorama is the recovery-aware personal context layer. The integration should make Strava activities more useful inside Diorama without trying to recreate the Strava experience.
Data strategy
Diorama normalizes Strava activities into its workout model, then reconciles them with Apple Health workouts. The user should not see duplicate cards, duplicate training totals, or inflated streak/load summaries when the same session exists in both places.
When a match is found, Diorama enriches the existing workout instead of inserting another one. The app should keep source metadata so users and support can understand whether the workout came from Apple Health, Strava, Garmin, Wahoo, Polar, Suunto, Peloton, or another upstream source when that information is available.
Swim handling
Swimming is a key reason to connect Strava, but it also needs careful expectations. Garmin-origin swims can show lap rows inside Strava's consumer app, yet the public API may not expose enough detail to build Diorama's full interval breakdown. Diorama should probe and label available data honestly instead of synthesizing intervals from a single aggregate swim.
User promise
Connect Strava to make workouts more complete, not more complicated.
Limitations
Strava data depends on what Strava exposes through its public API and what the upstream device sent to Strava. Not every activity includes route data, power, cadence, laps, splits, segment efforts, or streams. Diorama does not write workouts back to Strava or Apple Health. The integration is read-only. Strava pool swims should not be assumed to contain trustworthy interval rows. Apple Watch / HealthKit pool swims can provide length and interval detail; many Strava pool swims are aggregate-only through the public API.
Diorama
See your whole picture.
Diorama brings training, recovery, and health together so you keep competing — not just keep going.