Table 12.
Key issues and recommendations for mHealth app logging issues
Key issues found | Recommendations |
---|---|
- Complex or buggy signup health | - Implementing simple sign up health forms |
forms where users need to complete | and ensuring that the form is bug free. Along |
and submit too many health details or | with some integration to get the latest and |
information or face errors while enter- | most accurate users health details which comes |
ing their health data within the regis- | from other areas such as hospitals and GP clin- |
tration form | ics |
- Verification codes or OTP are not | - Implementing different ways for users to ver- |
properly delivered | ify their accounts besides OTP |
- Incorrect verification codes where | - Ensuring sending unexpired verification |
users get errors when submitting the | codes to users to complete the signup process |
verification code they have received | |
- Users not being able to retrieve their | - Allowing users to retrieve their user name in |
users’ names | case they forgot it |
- Users cannot reset their passwords | - Allowing users to sign in to the app using a |
since forgot passwords functionality is | passcode or face id |
not working properly | |
- The app keeps signing out, requiring | - Allowing users to keep being signed in as long |
users to log in each time | as they did not sign out |
- Users are trying to log in while the | - Allowing users to access the app status in |
app is temporarily down without hav- | case the app is down |
ing any information about the app er- | |
ror, so they end up resetting their ac- | |
count information |