Show data from companion app while activity is running (Glucose, Diabetic)

Former Member
Former Member
Am i wrong or isn't it possible to show data from an companion app while running an activity? If yes this really sucks.

I'm a diabetic and would like to show data from my Dexcom Glucose sensor in an activity which is really important for me.

If i understand it corretly it's only possible to create a whole new app and reimplement every datafield that i, or everybody else, needs?! That's stupid... Please tell me that I'm missing something.
  • There is no way to use data from a companion app with CIQ, and a data field can't use comm to get this info from the internet, so the only way to show this info is by doing a full blown watch-app (which can get the info using comm to the internet).

    Here's something in the store that I think does something like you are looking to do, and does it as a separate app. The developer first wanted to show the readings on a watchface, and started with a watch-app that looks like a watchface for the same reasons.

    https://apps.garmin.com/en-US/apps/531100b4-12ca-4828-865d-1f7064de498d
  • Former Member
    Former Member over 9 years ago
    Yeah i know that app but i've another easier way to fetch the data...
    But that really sucks. What is the real reason to not support communication in datafields? That does not make sense to me if i can rebuild the whole stuff anyway. It does just make it complicated to add functionality...
  • One thing is that on many devices, CIQ datafields can only be 16k, and there is overhead involved in comm - when the buffer is rec'd, it's converted into a dictionary, a whole much of memory is used. Also, think about management - what if two different DF's were both trying to do comm at the same time?

    A simple app can be done fairly easily. Look at the recording sample in the SDK. Most data you'd want to display is available in Act.Info, and most times, the only thing you may have to do is Statute to Metric conversions. The process of creating/starting/stopping/saving/discarding a recording is fairly simple too, as is enabling sensors (if you want to record HR for example).

    By "Companion app", do you mean another app on the watch, or do you mean one on your phone? (I've been assuming another app on your watch..)
  • Former Member
    Former Member over 9 years ago
    One thing is that on many devices, CIQ datafields can only be 16k, and there is overhead involved in comm - when the buffer is rec'd, it's converted into a dictionary, a whole much of memory is used. Also, think about management - what if two different DF's were both trying to do comm at the same time?

    A simple app can be done fairly easily. Look at the recording sample in the SDK. Most data you'd want to display is available in Act.Info, and most times, the only thing you may have to do is Statute to Metric conversions. The process of creating/starting/stopping/saving/discarding a recording is fairly simple too, as is enabling sensors (if you want to record HR for example).

    By "Companion app", do you mean another app on the watch, or do you mean one on your phone? (I've been assuming another app on your watch..)


    I mean a app on my phone or the garmin app used by "comm"