Skip to content

Firmware, Web Pages, User Interface, Usability Review #579

Description

@ForrestErickson

Is your feature request related to a problem? Please describe.
_A clear and concise description of what the problem is. Ex.

First problem
I'm always frustrated when a user interface does not convey if a field is an input or output or if when I look at a button to play or pause I know what the current state is.

Second Problem
There is another common problem like this:
is there a name for the ambiguity of when you cannot tell if a button on a video player will pause the play or start the play?

Describe the solution you'd like
A clear and concise description of what you want to happen.

All Krake hosted web pages should be reviewed for " low affordance"
See this AI description:
https://share.google/aimode/HDpH8Gc7ZxuxxmJh1

For the pause / play problem the AI suggests specific UX flaw is widely known as the "State vs. Action" ambiguity:
See this AI for details:
https://share.google/aimode/o36caGqrH9Pl1QdSG

For the
UX flaw is widely known as the "State vs. Action" ambiguity (or the State-Switch Dilemma).

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions