Table 9.

Problems that could not be directly addressed by system developers and which in turn had a proposed solution by the usability team.

Problem ID number	Problem	Scenario	System developer comments	Usability team proposal
1	The difference in operation between the home button and back button is not clear	User minimizes app	This is an Android design and cannot be changed and we feel that adding another button (an exit button) to the interface may cause further confusion	We will provide an instruction sheet that will show the user clearly the difference between the 2 buttons, emphasizing in particular that the back button is only used for uploading the data
3	Buttons on keypad are too small for this population	User logins to the app	This is an Android design and cannot be changed. The only solution would be to “buy” another keypad design that will be expensive	Short tutorials will be conducted for users on how to effectively use the keypad at the onset of use to improve confidence
5	Having to upload the data will be too hard to remember to do	Uploading data by exiting app	At this stage of development, an automatic data push is not feasible but will be considered for future	We will emphasize this scenario in our user manuals to reflect the fact that it needs to be carried out periodically
7	No prompt to indicate to the user that a manual connection is now required	User must connect to the insoles	We will improve the auto connection and introduce an option in the settings to turn off auto connection	We will describe the sequence in the short form manual, with steps for when a user should attempt a manual connection