Table 3.
Frequencies of barriers and facilitators for using the app.
| App-related factors | Barrier | Facilitator | ||
| Design and technical concerns | 9 | 4 | ||
|
|
No internet access | 2 | 0 | |
|
|
Adding medication: can add only half numbers or units (eg, 0.5) | 1 | 1 | |
|
|
Retrospective data entry not possible | 5 | 0 | |
|
|
Lack of notifications | 1 | 0 | |
|
|
Graphic display of blood glucose (trend) | 0 | 3 | |
| Characteristics of the innovation | 18 | 3 | ||
|
|
Ease of use or complexity | |||
|
|
|
Meal picker complex or not intuitive | 2 | 0 |
|
|
|
Sliders too sensitive | 2 | 0 |
|
|
|
Complexity of app, easy to use (NFSa) | 10 | 2 |
|
|
Relative advantage (usefulness) or lack | |||
|
|
|
No need to use additional booklet to register values | 0 | 1 |
|
|
|
NFS | 4 | 0 |
| Validity of resources | 9 | 2 | ||
|
|
Content available (completeness of meal picker) | 3 | 1 | |
|
|
Frequency of advice (eg, lacking between 2 meals) | 2 | 0 | |
|
|
Bolus suggestion | |||
|
|
|
Does not take into account blood glucose trend | 1 | 0 |
|
|
|
Incorrect, does not correspond to personal view | 3 | 0 |
|
|
Also bolus suggestion, even when blood glucose is (too) low | 0 | 1 | |
| System reliability | 3 | 0 | ||
|
|
Restarting the app takes too long | 1 | 0 | |
|
|
Login issues | 1 | 0 | |
|
|
Crashing (of app) | 1 | 0 | |
aNFS: not further specified.