You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the commonly used “calendar complication hack” no longer feasible as of WatchOS 10, a replacement for this would be massively valuable and impactful.
I’m thinking of the “rectangular complication”. Screen shot attached for current info I have in this complication, which includes:
Time of data pull
BG
Trend arrow
Delta
Loop status
24hr A1C estimate*
24hr Time in range %*
Current active basal
Insulin on board
Carbs on board
The two with * I think are not available today via Loop/LCG.
Other interesting data points I’ve toyed with are minimum predicted BG, maximum predicted BG, and eventual predicted BG.
Of course, the graph in the native Loop version of this complication is pretty to look at and has some good info baked into it, but it’s a bit tougher as it currently stands to understand min/max/eventual BG in that view for instance. If there was a way to get the visual graph while still delivering the data that’s needed, that’d be clever and beautiful.
The text was updated successfully, but these errors were encountered:
With the commonly used “calendar complication hack” no longer feasible as of WatchOS 10, a replacement for this would be massively valuable and impactful.
I’m thinking of the “rectangular complication”. Screen shot attached for current info I have in this complication, which includes:
The two with * I think are not available today via Loop/LCG.
Other interesting data points I’ve toyed with are minimum predicted BG, maximum predicted BG, and eventual predicted BG.
Of course, the graph in the native Loop version of this complication is pretty to look at and has some good info baked into it, but it’s a bit tougher as it currently stands to understand min/max/eventual BG in that view for instance. If there was a way to get the visual graph while still delivering the data that’s needed, that’d be clever and beautiful.
The text was updated successfully, but these errors were encountered: