Notes from the Bug Bash Session
Tom Clement Oketch
Confirmed Bugs
- View potential matches crashes if a new enquiry is not synced (Issue 218)
- Highlighted field labels display as ‘null’ for unverified users (Issue 219)
- Incorrect field types (Issue 220)
- Issue 129 was also re-identified, and subsequently additional context has been added to the pre-existing card
Feature Enhancements
- Replace notifications with labels
Currently all notifications on the android app are relayed as toast messages. These toast messages last only a little while and afterwards disappear automatically. The downside to this is that it is possible to miss critical messages especially when an error occurs. This enhancement replaces the most crucial notifications (regarding errors in logging in and syncing) with text labels which are persistent to ensure that the user always gets to see the errors encountered. An additional benefit that could be reaped from this is more deterministic testing.
- Misleading error messages on offline login
When a user attempts to login as a registered offline user and they do not specify the server URL, the offline login is successful but the user also sees the message Online login failed. Will try to login offline. When a user attempts to login as a registered offline user and they specify the server URL, the offline login is successful but the user also sees the message Invalid login credentials. Please try again. Some of the users who came out to test RapidFTR pointed out that these messages were confusing. This feature therefore seeks to replace the confusing error messages with more comprehensible ones.
- Nationality drop-down
For the location field Nationality, consider replacing the free text field with a drop-down that is pre-populated with the countries of the world. There should also be an option Other to allow users to specify any other emergent Nationality
- Use action bar instead of menu
A number of the newer android devices have no dedicated hardware menu button. However the RapidFTR mobile application assumes the existence of this button and actions such as Synchronise, Change Password and Log Out are dependent on the existence of this button. It is now recommended that designs are migrated away from using the menu button towards using an action bar to ensure that options previously presented as a menu are also available on devices with no hardware menu buttons
UX Issues
- Keyboard obscures most of the display area on some phones
On some phones, most notably the Huawei Ascend Y300, the screen display area was mostly obscured by the keyboard whenever a user attempted to enter text.
- Form section drop down is too close to Save
The form section picker/drop-down is too close to the save/edit button. As such, when selecting a form section using the drop down, it is very likely that the edit/save button will be pressed instead
- Save and Edit always take you back to the first form section
When viewing or editing a child or enquiry record on the mobile, clicking on edit/save will always open the corresponding view for the first form section. This behaviour is consistent regardless of the form section that was being viewed or edited at the time.
- Add a Spinner/Loading text when edit is pressed
When viewing a child or enquiry record on the mobile, pressing edit opens the edit view of the corresponding record without any transition or indication of loading. However when RapidFTR is running on a low-end phone, there is a noticeable delay in switching from the read-only view to the edit view. It is therefore worthwhile to display a spinner/loading message during this transition so that users are aware that the app is working and has not become unresponsive. Note such a transition already exists when the save button is pressed.