Mobile app heuristics evaluation by hyena labs studio
11 likes2,809 views
The document provides a heuristic evaluation of tasks in a mobile application. Three key tasks are analyzed: viewing daily targets, placing store orders, and making party-wise collections. A total of 95 usability issues were identified across the three tasks. Issues were highest for consistency and standards (15 occurrences), followed by user control and freedom (10 occurrences). Most issues were rated as medium severity (23 occurrences), but there were also issues rated as high (13 occurrences) and severe (8 occurrences). The evaluation provides recommendations to address the usability issues identified.
Mobile app heuristics evaluation by hyena labs studio
- 1. Hyena Labs Studio Heuristics Evaluation of Mobile Applications Hyena Labs Studio | www.hyenalabs.com
- 2. Heuristics Evaluation based on Tasks 3 tasks are analyzed in this heuristic evaluation, focusing on the following screens in detail: - Log In - Day Targets - Order Booking - Collections and Party Wise Collections User Goal: To reach the target set by the regional distributor User Tasks: - Look at daily targets - Place an order at the store - Make a party wise collection Slide 2
- 3. Task: Look at daily targets Hyena Labs Studio | www.hyenalabs.com3 Slide
- 4. 1 Step 1 5 Issue: The alignment of the fields makes it difficult to scan through. Recommendation: Left align the fields to allow users to scan through easily. 1 2 4 3 Severity: Low 5 Heuristic Principle: Flexibility and efficiency of use 2 The background area of the login text field is Issue: blue which makes it look disabled. Recommendation: Replace the blue background of the 4 There is no keyboard input cue for users to Issue: login field to white to enhance perceptual data entry. enter the data. Severity: Low Recommendation: Provide a visual input for data entry while filling in the username and password. Heuristic Principle: Error Prevention Severity: Medium Heuristic Principle: Visibility of system status 3 The path to move ahead is difficult to access. Issue: 5 There are 2 placeholders for one brand identity. Recommendation: Fitts’ Law mentions that important Issue: accessible buttons need to be large and easy to click. Recommendation: Provide one placeholder for the HUL Severity: Low brand. Heuristic Principle: User control and freedom Severity: High Heuristic Principle: Recognition rather than recall Slide 4
- 5. 6 Step 2 Issue: This step can act as an irritant with users having to click on the image. Recommendation: Avoid the use of a click on the welcome screen. Severity: High Heuristic Principle: User control and freedom 6 Slide 5 Slide 5
- 6. Step 3 7 The horizontal scroll makes the data difficult to Issue: access. Recommendation: Avoid the use of horizontal scroll. Severity: High Heuristic Principle: Flexibility and efficiency of use 8 8 The information is difficult to scan with the Issue: number of colors used. Recommendation: Use icons/symbols. Change the tabular structure to a list. Severity: Medium Heuristic Principle: Aesthetic and minimalist design 7 9 9 The menu navigation is inactive. Issue: Recommendation: Activate the navigation of the menu. Severity: High Heuristic Principle: Consistency and standards Slide 6 Slide 6
- 7. Task: Place an order at the store Hyena Labs Studio | www.hyenalabs.com7 Slide
- 8. Step 1-9 Step 1: Main Step 2: Day Dashboard Step 3: Beat and Outlet Step 4: Outlet Info Step 5: Merchandising Menu Issue: The number of steps to reach the order booking screen is too long. Recommendation: Allow minimum number of steps to reach the order booking screen. Severity: Severe Heuristic Principle: Flexibility and Step 6: VisiBook Step 7: QOC Goals Step 8: IQ Goals Step 9: Stock Check efficiency of use Slide 8 Slide 8
- 9. Step 10 1 The ‘Lines’ label probes an input field when it Issue: cannot be edited. 1 3 2 Recommendation: Information elicited should not probe editing. Avoid the use of a text field. Severity: Medium Heuristic Principle: Consistency and standards 4 2 The ‘Total Val’ label probes an input field when Issue: it cannot be edited. Recommendation: Information elicited should not probe editing. Avoid the use of a text field. Severity: Medium Heuristic Principle: Consistency and standards 4 The all caps font makes it difficult to scan. 3 The keyboard when activated does not provide Issue: Issue: the entry for numbers. Recommendation: Provide all fonts in upper lower case Recommendation: Allow number entry to be intuitive on to enhance readability. the keyboard. Severity: Severe Severity: Severe Heuristic Principle: Recognition rather than recall Heuristic Principle: Match between system and the real world Slide 9 Slide 9
- 10. Step 10 5 There is no path that leads back to this screen Issue: once “G” is selected. The back button leads to 7 the QOC Goals screen. Recommendation: Provide a navigation path for users come back to the previous screen. Severity: Severe Heuristic Principle: Error prevention 8 6 This step adds to an extra click in navigation. 5 Issue: Recommendation: Allow the system to save information automatically without users having to save it. Severity: Severe 6 Heuristic Principle: Error prevention 8 It is unclear that there are choices that can be 7 Users would need to look under the packs to Issue: Issue: made under units and dozens. view the order. Recommendation: Avoid placing several actions under Recommendation: Place viewing the order outside of the one button. dropdown to make it accessible. Severity: High Severity: High Heuristic Principle: Recognition rather than recall Heuristic Principle: User control and freedom Slide 10
- 11. Step 10 9 The action to click on a tab to get the number Issue: pad is unintuitive. Recommendation: Place a visual aid to help users know that the number pad can be seen when clicked. Severity: High 9 Heuristic Principle: User control and freedom 10 The ‘STK’ and other labels probes an input field Issue: when it cannot be edited. Recommendation: Information elicited should not probe editing. Avoid the use of a text field. 10 11 Severity: Medium Heuristic Principle: Consistency and standards 11 The message that appears does not provide Issue: information. It is merely an alert. Recommendation: Avoid using pop ups that behave like alerts. Severity: Medium Heuristic Principle: User control and freedom Slide 11
- 12. Step 10 12 While entering in the input, the system does not Issue: 13 provide a suggestion. 12 Recommendation: Provide suggestions while the user looks for a stock. 15 Severity: Medium Heuristic Principle: User control and freedom 13 There is no confirmation that the order has Issue: been taken. 14 Recommendation: Provide a button to affirm that the order has been taken. Severity: Medium Heuristic Principle: Match between system and the real world 15 There is no option that allows users to view Issue: 14 “All packs”. Along with this, filtering is not Issue: The exit button does not appear on all pages of possible. the application. Recommendation: Allow users to filter and view options Recommendation: Place the exit button consistently simultaneously. Provide an option called “All Packs”. across the application. Severity: High Severity: High Heuristic Principle: Match between system and the Heuristic Principle: Consistency and standards real world Slide 12 Slide 12
- 13. Step 11-12 16 Issue: The navigational items on the page are not consistent when interaction 16 takes place through the application. Recommendation: Allow a consistent navigation interaction through the application. Severity: High Heuristic Principle: Consistency and standards Step 11: Order Summary Step 12: Take Back / Damages Slide 13
- 14. Task: Make a party wise collection Slide 14 Hyena Labs Studio | www.hyenalabs.com
- 15. Step 1 1 The ‘Party Wise’ and ‘Bill Wise’ labels are Issue: encircled by text fields which makes it look editable. Recommendation: Provide the radio buttons without the text field. Severity: Low Heuristic Principle: Consistency and standards 1 2 The exit button does not appear on all pages of Issue: the application. Recommendation: Place the exit button consistently across the application. 3 2 Severity: High Heuristic Principle: Consistency and standards 3 There is no path that leads back to this screen Issue: once “G” is selected. The back button leads to the QOC Goals screen. Recommendation: Provide a navigation path for users come back to this screen as this is the task at hand. Severity: Severe Heuristic Principle: Error Prevention Slide 15 Slide 15
- 16. Step 2 4 The alignment of the fields do not match. Issue: Recommendation: Left align all fields, including ‘O/S’ and ‘Days’. Severity: Low Heuristic Principle: Consistency and standards 5 4 5 There are no items in the list to scroll but it is 5 Issue: provided as an element on the screen. Recommendation: Avoid using the scrollbar when there 6 are no items to scroll. Severity: Low Heuristic Principle: Consistency and standards 6 The alignment of the fields do not allow efficient Issue: scanning. Recommendation: Left align all fields. Severity: Low Heuristic Principle: Consistency and standards Slide 16
- 17. Step 2 7 The labels probe an input field when it cannot Issue: be edited. Recommendation: Information elicited should not probe editing. Avoid the use of a text field. Severity: Medium 7 8 Heuristic Principle: Consistency and standards 8 There are no items in the list to scroll but it is Issue: 8 provided as an element on the screen. 9 10 Recommendation: Avoid using the scrollbar when there are no items to scroll. Severity: Low Heuristic Principle: Consistency and standards 9 There is no path that leads back to this screen Issue: once “G” is selected. The back button leads to 10 The exit button does not appear on all pages of the QOC Goals screen. Issue: the application. Recommendation: Provide a navigation path for users come back to this screen as this is the task at hand. Recommendation: Place the exit button consistently across the application. Severity: Severe Severity: High Heuristic Principle: Error Prevention Slide 17 Heuristic Principle: Consistency and standards Slide 17
- 18. Step 3 11 The terminology used “PNC N-2” is unfamiliar Issue: and cannot be understood without training. Recommendation: Avoid using jargons. Easily understood terminologies prevent errors. Severity: Medium Heuristic Principle: Match between system and real world 11 12 The user would not expect a calendar input in Issue: this field which appears unknowingly. Recommendation: Provide the calendar as a visual cue, 13 upfront. Severity: Medium Heuristic Principle: User control and freedom 13 The calendar input does not need an ‘ok’ as an Issue: option. 12 Recommendation: The ‘OK’ option adds to the number of clicks. Allow users to double click on the date. Severity: Medium Heuristic Principle: Match between system and real world Slide 18
- 19. Analysis Slide 19 Hyena Labs Studio | www.hyenalabs.com
- 20. Summary of Recommendations Low Left align the fields to allow users to scan through 1 easily. (3) 16 Avoid placing several actions under one button. Medium Replace the blue background of the login field to 2 white to enhance perceptual data entry. 17 Provide one placeholder for the HUL brand. High Fitts’ Law mentions that important accessible 3 buttons need to be large and easy to click. 18 Avoid the use of a click on the welcome screen. Severe Allow users to filter and view options simultaneously. 4 Provide the radio buttons without the text field. 19 Provide an option called “All Packs”. Avoid using the scrollbar when there are no items Allow a consistent navigation interaction through the 5 to scroll. (2) 20 application. Provide a visual input for data entry while filling in 6 the username and password. 21 Activate the navigation of the menu. Use icons/symbols. Change the tabular structure Place viewing the order outside of the 7 to a list. 22 dropdown to make it accessible. Information elicited should not probe editing. Avoid Place a visual aid to help users know that the number 8 the use of a text field. (3) 23 pad can be seen when clicked. Provide suggestions while the user looks for Place the exit button consistently across the 9 a stock. 24 application. (3) Provide a button to affirm that the order has The welcome screen can be omitted 10 been taken. 25 completely. Allow number entry to be intuitive 11 Avoid using pop ups that behave like alerts. 26 on the keyboard. Avoid using jargons. Easily understood terminologies Provide all fonts in upper lower case to enhance 12 prevent errors. 27 readability. Provide a navigation path for users come back 13 Provide the calendar as a visual cue, upfront. 28 To the previous screen. (3) The ‘OK’ option adds to the number of clicks. Allow users to Allow the system to save information 14 double click on the date. 29 automatically without users having to save it. Allow minimum number of steps to reach the order 15 Avoid the use of horizontal scroll. 30 booking screen.
- 21. Analysis and Reporting Place an Make a Low: 1 Look at daily order at the party wise Total Heuristic targets store collection Occurrence Medium: 2 Visibility of system status 2 - - 1 Medium 3 Medium High: 3 Match between system and 1 High the real world - 9 4 1 Severe Severe: 4 1 Low 3 Medium User control and freedom 4 10 2 3 High 5 Low 5 Medium Consistency and standards 3 12 15 5 High 1 Low Error prevention 1 8 8 4 Severe Recognition rather than 2 High recall 3 7 - 1 Severe 1 Low Flexibility and efficiency of 1 High use 4 4 - 1 Severe Aesthetic and minimalist design 2 - - 1 Medium Users recognize, diagnose, and recover from errors - - - - Help and documentation - - - - 5 Low 3 Low 6 Medium 5 Medium 2 Medium 6 High 2 High Total Issues 4 High 5 Severe 2 Severe 95
- 22. Look at daily targets Slide 22
- 23. Place an order at the store Slide 23
- 24. Make a party wise collection Slide 24
- 25. Total Occurrences Slide 25