Try to keep actions in proximity whenever possible.
In your mock, if you go with a single button (or even a second button below), users have to perform several steps:
Select a row
Move the mouse down to the now changing button ('update'). The more workstations added, the further this button change appears from the selected row. They also have to notice this ...
Phrase tasks from the participants perspective not knowing about the IA of the application/site.
Task goal: Use the location finder tool (labeled Find a Branch)
Leading user task: Find a branch near you and see when it is open tomorrow.
Improvement: When is the bank location that’s most ...
Say if it's a travel site, tell them to book a flight and a hotel.
Just give them the final objectives.
And then tell them to "think aloud" ( not what they think about xyz, but "I am pressing the red button")
If you want to ask questions as you go along you end up asking mangled English "why did you press the 'thing,' you just ...
Start by asking them to think out loud
Then keep the monologue going:
Tell me what you are seeing on the screen Tell me what do you thing
that thing that you are seeing does etc.
You can find out more here:
As a general rule, try to avoid using the labels for your sections. I've found that testers use your wording as a guide and focus on searching that word in the labels instead of doing the mental work of guessing where to find it.
To avoid this, describe things you can do inside the section, or content it might contain that would be beneficial for the user to ...
A quote that is seen a lot is:
“If we want users to like our software, we should design it to behave like a likeable person: respectful, generous and helpful.”
— Alan Cooper, Software Designer and Programmer
The flow described is not helpful and even a bit disrespectful to the user.
Not so much of a principle, but it would fail a Task Analysis since it removed the user from achieving their goal.
Taskflow Analysis - https://methods.18f.gov/decide/task-flow-analysis/#:~:text=A%20step%2Dby%2Dstep%20analysis,in%20pursuit%20of%20their%20goal.
Additionally, a somewhat related principle is that of Reciprocity, dicussed here - https://www....
You need to reconsider the metaphor you are using.
You've chosen "Allow diagonal" and "Force horizontal" which is a difficult dichotomy to handle. The two terms don't directly communicate two different states of a single value. With these terms it's going to be difficult for anyone to figure out what state a filled or empty checkbox ...
Here is the problem: The activation toggle isn't communicated as a setting but as a switch to toggle the panel on or off.
Make it part of the form by placing it as the first setting above the others. Make it more prominent if needed with color, increased size, heavier font-weight, etc. Whatever suits the design. Also, the label should be clear. Something ...
Toggles communicate, “This change takes place immediately.” It might be struggling against your Save button.
What you could do is use another pattern for the status toggle - could be another radio button set with Active and Inactive labels — and put that with the other controls, maybe right above the Cancel and Save buttons. That way, everything that can be ...
There are multiple ways to solve this, and the solution largely depends on the context & which action the user will use frequently. To create a more flexible layout for accordion will be to move the chevron(^) to the left along with the name.
Free-up the space for other actions on the right. If delete is the primary action, keep the icon outside & ...
What might be trendy might not be user friendly. For instance, the hamburger used to be 'trendy', however it has known usability issues. This will also depend on your main audience. what age group are they? You could test both options on your audience to get their feedback.
When in question, I'd advise you to go for the safer and more obvious choice.
This seems to be an issue with how login is handled across both the systems, rather than a UI issue. If your application cannot share login status and credentials with the third party tool, then this problem will persist.
One workaround is to retrieve the search results from the 3rd party search application, and display that within your react library ...
I'm also guessing you have already done something but could help others.
You can go back to previous steps in the stepper to edit what you previously had and we have the ability for the user to click the title or an edit icon next to it. However the person providing feedback (director in this case) said that they felt they should look more like full size ...
The situation is not ideal, and there's no elegant way out -- but you don't need to direct your users to reinstall the app either. You can send them to the settings panel for your application, where permissions are managed, and they can revise their decision.
After detecting this is the case, you might show a dialog (to create the expectation), then ...
We have a similar situation in our e-commerce app for the product's categories.
At the top there's a button to Add a New Item to root
If an item contains subitems, there is an expand-collapse icon on the left (the little triangle)
When hovering an item or sub-item a right bar appear with these options:
Plus icon = Add New Sub-item
Zoom icon = Item Info
atleast 32 is important and also it would anyway help with the branding/Logo/etc. if theres nothing much in navigation
We have been so accustomed to a navigation that even for SPAs we have navbar that would just help user vertically scroll.
I do believe it should be 40px but 32 is also good.
I think we should keep all three buttons
and it should be Okay | Cancel | Help
it this is a repetitive activity people would most likely wanna hit okay
Help and cancel have less chances hence the above priority should be better
Hope this helps!