API for history of recorded activities on device

Hello,

In short: is it possible to retrieve the recorded activities (e.g. running, biking, etc.) with the Garmin IQ API?

I have searched for hours, in the API docs (it is not in PersistentContent or ActivityRecording) on the forum and a similar app in the IQ store. Nothing that gives information on the recorded activities.
A little background on what I am trying to do: I would like to make a widget that displays a chart of the lap times of the last activity. This could be cool information to analyse your activity. This information is of course stored as FIT files on the device and I would expect that the IQ API exposes some methods to access these files. Any ideas?
  • No, there is no access to that data on the device.

    The closest you can get is to use a web service to access the data that the user has uploaded. As examples, you could use the Garmin Connect API, the Strava API.

    Travis
  • I would like to make a widget that displays a chart of the lap times of the last activity. This could be cool information to analyse your activity.


    Your lap times from the most recent timed activities are visible in the History section of most watches that support Connect‑IQ, albeit not graphically but just as numbers, if I'm not mistaken.

    I also don't quite get why you would want it as a widget (which is automatically dismissed after so many seconds) instead of a watch app.
  • I also don't quite get why you would want it as a widget (which is automatically dismissed after so many seconds) instead of a watch app.

    This should be fine for a widget. The widget timeout only applies if you are not interacting with it... If it takes more than a 10-15 seconds to process the information on a single screen, the app isn't designed well.

    Travis
  • As Travis said, the widget revert timeout on wearables is sufficient in most cases to get the data you want for a "quick view". Doing Comm from the internet, etc. With 2.3.x and the f5 family and 935, you can also have a background process that runs even if you're not running the widget. I'm using one right now that gets weather data off the net every 15 minutes, so when I go to the main widget, the data is right there right away... No delay at all.