UI papercuts
See original GitHub issueA few minor UI issues I came across testing the app
- The icon and text should be centered together on the empty state buttons
- All button labels should use title case
- I’d maybe make the “take a shot” label more explicit, “shot” is a bit vague. How about “Take a Screenshot” or “New Scan”?
- The action bar should have a divider line above
- The buttons in the action bar should not be raised, i.e. have no background unless hovered/active
- The “take a shot” button should probably have the
.suggested-action
class
- The “Configure” menu item could be more explicit, e.g. “Manage Languages”
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Papercuts - Small but painful! [UX/UI] | by Sanchita Srivastava
In conclusion, papercuts are almost unavoidable and will definitely creep into the UI during the course of development, may also be overlooked during...
Read more >UX Papercuts | Daniel Gross
What you're doing here is both decreasing cost (fluid, always-on UI) and increasing the reward (social affirmation) required in order to give feedback....
Read more >Paper cut bug - Wikipedia
In usability and interaction design, a paper cut bug is defined as "a trivially fixable ... others rely on regular practices to encourage...
Read more >Software Paper Cuts - Matthew Bischoff
Missing Animation: Rather than smoothly animating to a new state, the UI blinks and updates, like an unfortunate smash cut. No Errors or...
Read more >Blender UI paper cuts - User Feedback - Blender Developer Talk
We would like to collect a list of UI papercuts in this thread for reference. What is a papercut? A small, isolated UI...
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
Yep, since you think your issue is done, I’ll move this one to its own issue and plan it for the next release.
Nice, yeah the points from the original issue all look fixed to me!
I agree with @jannuary’s suggestions about the language dialog, but maybe that should be a separate issue if it’ll be redesigned soon?