Feature Request: API Support for Multisport Transitions in Native Swimrun Activities
Category: Connect IQ SDK
Type: Feature Request / Missing API Capability
Platform: Garmin Connect IQ / Monkey C
Activity Profile: Native Swimrun / Multisport
1. Summary
The Garmin Connect IQ SDK does not appear to provide a documented API for programmatically triggering a sport transition within an active native Swimrun or Multisport activity.
Currently, transitions between swimming and running must be initiated through the watch’s native controls.
We would like to request an API that allows a Connect IQ application or data field to request advancement to the next sport in an existing native multisport activity.
2. Current Behavior
The Connect IQ SDK provides the onNextMultisportLeg() callback for detecting multisport transitions.
However, this callback only notifies the application after a transition has occurred.
There appears to be no corresponding public API for initiating the transition.
3. Expected Behavior
A Connect IQ application or data field should be able to request a transition to the next configured sport without interrupting the native activity recording.
For example, a hypothetical API could be:
Multisport.requestNextLeg();
The Garmin activity engine would remain responsible for validating and executing the transition.
4. Use Case
A Connect IQ data field running within the native Swimrun profile may need to request a transition between swimming and running.
Currently, the application can detect transitions but cannot initiate them.
Providing this capability would enable additional functionality while preserving Garmin’s native activity recording and multisport FIT structure.
5. Questions for Garmin
- Is there an existing supported API for initiating a native multisport transition?
- Is the absence of this capability an intentional SDK limitation?
- Could a future Connect IQ SDK expose a method for requesting the next multisport leg?
- Could this functionality be supported within Connect IQ Data Fields?
6. Requested Enhancement
Please consider exposing a documented API for requesting sport transitions within native multisport activities.
The API should preserve Garmin’s existing activity recording behavior and FIT file structure.
This would provide greater flexibility for Connect IQ developers without requiring a separate activity recording implementation.
