Table 2.
Summary of Open Response Questions.
| Smartphone applications used | |
|---|---|
| Application | n |
| Dexcom | 27 |
| MyFitnessPal | 12 |
| Loop/LoopKit | 12 |
| RapidCalc | 8 |
| Diabetes:M | 6 |
| CalorieKing | 5 |
| PredictBGL | 5 |
| One Drop | 5 |
| AndroidAPS | 5 |
| xDrip | 4 |
| Nightscout | 3 |
| Other apps with ≦ 2 respondents | 29 |
| Why did you stop using the phone application? | |
| Reason | n |
| Pump use | 53 |
| Too long/cumbersome | 23 |
| I can do it in my head | 11 |
| Technical issues/poor user experience | 10 |
| Inaccurate | 10 |
| No longer needed it | 7 |
| Insurance coverage and/or cost | 5 |
| Medicare doesn’t cover Dexcom App | 4 |
| Unavailable on current phone platform | 4 |
| Changed diet | 3 |
| For a study or beta testing | 3 |
| Annoying alarms | 2 |
| No value provided | 2 |
| Fell out of the routine | 1 |
| Geared for younger age group | 1 |
| Additional features to include in a phone app | |
| Suggestion | n |
| App compatibility | 159 |
| Customizable alert settings | 93 |
| Data review | 91 |
| Insulin dose adjustments | 57 |
| Data sharing | 55 |
| Carb counting | 48 |
| Predicted trends in glucose | 45 |
| Decreased user input | 30 |
| Insurance coverage and/or cost | 28 |
| App specs: battery, memory, GUI | 16 |
| Emergency alert | 14 |
| Insulin-on-board | 13 |
| Low vision compatibility | 2 |
Abbreviation: GUI, graphical user interface.
There were 112, 132, and 595 unique respondents for each question respectively. App compatibility included many mentions of a phone app to perform insulin pump functions as well as the desire for an app to automatically import data from peripheral devices.