Apo’en giver et rigtigt fint overblik over de indsamlede data fra sensorerne. Dette er både med tid i det fastsatte målområde, gennemsnit og grafer der dækker både dage, uger og måneder. Desværre er der mange fejlskanninger, hvor apo’en giver feedback om at skanningen er fortaget, men ingen data er indlæst.

Jeg synes den er en overskueligt mængde data som bliver præsenteret på en intuitivt måde. Jeg er nok ikke den første men savner funktionen hvor data er overført til mobilen/ur/cykel computer uden skanning. Kan se v2.10 af appen er i UK app store men hvorfor er det ikke tilgængeligt i den DK app store, eller hvornår kan man forvent den? Det ville være en game changer for mig og mange andre med at forbedre livs kvalitet.

Super fin app, der giver et godt overblik over Glucose niveau i hverdag. Alvorlig mangel på muligheder for samvirke med smartwatch!!!!

I am not aware of any other way to give feedback to your software department, so this will have to do…On a general note, I beleive that you could benefit from more diabetic people in you QA group, to get a an app that solves more issues and is more user friendly.Now, on to specifics (sorry for the formating, but unfortunately the appstore have severe limitations on this…):1: Additional alarms, with aditional sounds (5-10 different sounds to choose from would be appreciated) specific to the alarms would be apreciated.1a: A specific alarm for LO, that triggers every god damn minute my curret reading is LO, no matter if I have acknowledged it previously. I do not care, if I acknowledged “low blodglukose” when I was at 3.2, I NEED to know when I reach LO. This should be a straight forward implementation with a flag and a timer. Possibility to adjust the time interval would probably be a good idea, to suit as many users needs as possible.1b: Different alarms for “High blodglucose” and “Very high blodglucose” with different alarm sounds. Once I have acknowledged a “High blodglucose” at 8.6, I would like a more severe sound once I reach 11.0.1c: A timer to give continues alarms every x minutes on both high and low glucose, both individually adjustable to, say, 1-30minutes.2: More options on estimated 1ac. I would like to change between 7, 14, 30, and 90 days, I know that the accuracy will be vastly lowered on fewer days, but I would like to see if I am on the right track, and where I would end up if I continue down the current path.3: Please fix the issue, where communication breaks down on iOS updates… This is the only data protocol I have ever witnessed break down when I install a security update. I do not know how the protocol is structured, or what causes the breakdown, but the issue clearly lies on app-end, as the issue seems to get fixed when the app updates. This does not seem to be an issue on other protocols, my BT heaset have never disappeared on a iOS update.