Training can sync while Kestivo is closed.
Previously, much of the completed-activity synchronization depended on launching Kestivo on the iPhone. It worked, but it meant that information about a morning workout might not reach the coaching system until the athlete opened the app hours later.
Kestivo now has server-side background synchronization through the existing Intervals.icu integration. Real activities have arrived while the iOS app was closed, without requiring a manual foreground sync.
This week also brought work on multi-athlete reliability. The scheduler can safely process more than one athlete in a run, preserve account boundaries, and avoid creating duplicate activities when synchronization repeats.
Background processing is now operational, although its timing still depends on the connected service and normal infrastructure conditions.
The first completion notification arrived.
Automatic activity ingestion makes a simple but useful interaction possible: after a newly imported workout is recorded, Kestivo can notify the athlete that it has been received.
The first real Workout completed notification has now reached an iPhone. The message is deliberately generic, so training and health details do not appear on the lock screen. Its action can open the corresponding authenticated Activity Details.
Designed for everyday use
- Opt-in delivery
- Run, Bike and Swim import eligibility
- Privacy-safe lock-screen text
- Direct route to Activity Details
Deliberate safeguards
- Notifications for new imports, not every repeat sync
- Active device and preference checks
- Bounded age and retry rules
- No need to wait for intensity analysis
Kestivo Web is becoming a real application.
In the previous update, Web existed mostly as a technical foundation. It has now advanced to a private, protected browser environment where the owner can sign in to an existing Kestivo account and inspect real training data.
The experience is still read-only, but it already covers key parts of the coaching workflow.
The desktop layouts received another round of refinement. The Training Week is more compact, planned and completed sessions are shown distinctly, and workout details retain the separation between prescription and recorded evidence.
Web is not a public beta yet. Access remains restricted to private owner testing. The iOS app continues to be the main beta product, with both clients designed to share the same authoritative coaching data and logic.
Making automatic processing less fragile.
As more training arrives without an app launch, Kestivo needs to handle delayed and incomplete information more carefully. A temporary upstream gap should not be mistaken for a permanent failure. Equally, an unavailable source should not lead to endless automatic retries.
This week's changes improve how background jobs handle their prerequisites, recover when eligible information becomes available, and keep activity load, daily load and physiology processing aligned with recorded training.
Processing distinguishes a genuinely unavailable automatic source from data that may arrive or become complete later.
Retries and recovery operate within controlled limits rather than launching unrestricted work.
Background imports preserve owner isolation and avoid duplicate training records.
Completed activities can contribute to updated training load and physiology without repeated screen visits.
Most of this is invisible by design. Its value is having more dependable training context ready for the next coaching decision.
From knowing what happened to knowing what should change.
Recent work has improved Kestivo's ability to compare planned and completed sessions, maintain training load and physiology, and now retrieve new activities in the background.
The next major coaching challenge is deciding what to recommend when the week does not unfold as planned. A harder-than-prescribed ride, a missed run or an unexpected training day should be assessed in the context of the wider week, not treated as a calendar-editing exercise.
Kestivo is getting stronger at the first two questions. The long-term goal remains an explainable recommendation for the third, with the athlete retaining final approval of any plan change.
Help shape Kestivo's next steps.
The iOS private beta is open to selected athletes. Join the waitlist for future TestFlight places and Kestivo development updates.