Heuristic Evaluation
As of the current day & version (18.01.2026) of our Kotlin-based app, we analyzed and looked for possible problems and issues we encountered, which later on next week we can work on, including the qualitative feedback we will gather.
10 Usability Heuristics
- Visibility of System Status
- Match Between System and the Real World
- User Control and Freedom
- Consistency and Standards
- Error Prevention
- Recognition Rather Than Recall
- Flexibility and Efficiency of Use
- Aesthetic and Minimalist Design
- Help Users Recognize, Diagnose, and Recover from Errors
- Help and Documentation
Identified Issues
| Issue | Description | Heuristic | Severity |
|---|---|---|---|
| 1 | The current API performance is relatively slow when searching huge amount of cards | 7 | 3 |
| 2 | The user won’t be able to find a specific card just by typing the Pokemon’s name | 6, 7 | 4 |
| 3 | Currently not all Pokemon cards can be displayed when searching for a specific Pokemon (cap at 20 per page) | 1, 3, 5 | 3 |
| 4 | It might be confusing for first-time users to search for valuable cards in the Graph screen | 6 | 1 |
Severity Scale
- 1: Cosmetic problem only
- 2: Minor usability problem
- 3: Major usability problem
- 4: Usability catastrophe
Planned Improvements
Based on the identified issues, we plan to:
- Optimize API calls and implement caching for better performance
- Enhance search functionality with autocomplete and fuzzy matching
- Implement pagination or infinite scroll for comprehensive card listings
- Add onboarding tooltips and help documentation for complex features