Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error reports: UI hides actions and does not follow UI standards
See original GitHub issueThe error reporting UI hides links and actions for ID History and privacy notice
The user does not know what can be clicked or activated.
Avoid duplicates
- This enhancement request has not already been raised before
- Unknown if apple problem. I have only an Android phone. I did look and there is no similar bug in the
documentationrepo.
Current Implementation
- menu -> app information
- click error reports
- scroll to bottom of UI
Only the Start button is clickable. Nothing else is visually clickable or actionable.
There are 8+ paragraphs of text on this UI. The UI must follow UI standards to indicate what is clickable/actionable.
Suggested Enhancement
- menu -> app information
- click error reports
- scroll to bottom of UI
- ID History uses the “further indicator” to lead the user to activate it for a list of IDs
- Privacy notice is underlined indicating a link to content.
Good examples…
Expected Benefits
- Less user confusion. A user in this section of the app wants to help. But the lack of standard UI guidelines hides functionality and leads to user confusion and/or abandon.
- Faster turnaround/escalation. When the functionality is not hidden, then the user can quickly report the error. Since this is a live service related to country-wide healthcare, timely reporting of problems is relevant.
- Less support resources/humans. Escalation to support/github because of the hidden functionality consumes further human resources.
Internal Tracking ID: EXPOSUREAPP-12854
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to design and convey error messages properly - Bootcamp
Guidelines for error messages. The following are based on error messages guidelines created by Microsoft and Apple.
Read more >Should unauthorized actions in the UI be hidden, disabled, or ...
If I have actions that I know a user will not be able to perform due to insufficient privileges or object state, should...
Read more >Error prevention in UX design: How Facebook and Gmail get it ...
Mailchimp demonstrating error prevention by asking users to type DELETE to confirm their actions. As you can see from the image above, unless...
Read more >Top 10 Application-Design Mistakes - Nielsen Norman Group
1. Poor Feedback. One of the most basic guidelines for improving an application's usability is to provide clear feedback: · 2. Inconsistency ·...
Read more >Human Interface Guidelines - Design - Apple Developer
Human Interface Guidelines. The HIG contains guidance and best practices that can help you design a great experience for any Apple platform.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for your enhancement request @diablodale. We have created an internal ticket for it and will raise this topic internally. Internal Tracking ID: EXPOSUREAPP-12854
Corona-Warn-App Open Source Team
In https://github.com/corona-warn-app/cwa-wishlist/issues/523 I included the following sentence under “Suggested Enhancement”:
The error reports UI in general should be improved.