Table 7.
Key issues and recommendations for mHealth app stability issues
| Key issues found | Recommendations |
|---|---|
| -users encounter bugs while analysing | - Developers need to proactively analyse user |
| or processing their mHealth data | reviews and addressing key reported bugs to |
| ensure health dependent end users are not se- | |
| riously impacted | |
| - Apps crashing/freezing when process- | - Ensuring the existence of enough computa- |
| ing and mining specific mHealth tasks | tional power based on the users data size; test- |
| ing practices need to include range of realistic | |
| mHealth app user datasets and loadings | |
| - Some mHealth functionalities get | - mHealth users become dependent on apps for |
| buggy only after developer updates | health needs and hence all functionalities need |
| stringent testing across multiple devices before | |
| releasing updates |