6

We had a similar problem at the project I am currently working on. We decided that the breadcrumbs should represent the static hierarchy of pages - rather than the user's history. When representing the history of visited pages, the path would soon get confusingly complex, because search features, cross-links, etc. can generate a lot of redundancy. On the ...


5

I feel like you're going about this the wrong way, you should ask the creator of the button, prior to any implementation, the questions if it fundamentally relies on them being in the right country and having registered for Stripe, something like this: This prevents them from placing a button that potentially would not work, on their site in the first place....


3

I believe when the user clicks on the button save and the second block is empty, don't need validation because it's not a priority for the user the fields empty. If he clicks on the button accidentally he can finish the task and if he needed the second block and forgot, he can edit this information later.


3

My viewpoint: Save button on the bottom. The flow should follow natural behaviour. The user will click on the save button after filling the form and then naturally the action should be there, after form. But if you not confident about this, please add both, on the top and on the bottom. You could create 2 stages of verification: If any data was filled on ...


2

One approach is to have the default filter set to the most common search, and have users be explicit about the starting dimension. In the sketch below, I'm suggesting some friction up front aiming for more clarity about the dependent relationships. You could make them explicitly select the starting search: By country (which then shows only the Orgs) By ...


1

What do breadcrumbs do? -Show how the user navigated to a particular page -Show the hierarchy of a page If a page has multiple different parents, identify a canonical path to it in the site hierarchy and show that path in the breadcrumb trail. Don’t attempt to personalize the breadcrumb trail so that it will reflect each user’s individual path within the ...


1

If there's a concept of default product, have that selected (and moved to the top). Or, just have the first product selected. I don't see any viable reason for not having anything selected. Clicking on the product shouldn't enable/disable as it isn't clear what the checkbox does. I would refrain from using the exact same pattern as the browser because ...


1

I would argue that it's very hard to know how your audience will respond to your (somewhat involved) setup process. That being said, one of the versions you describe (the kind where each step in the process is on a single view, in sequential order), will give you feedback as to where users are struggling – either through in-person user testing, or via ...


1

TL;DR: Functionally, there should be little-or-no difference between top-level containers1 ("groups") and lower-level ones. However, it may be useful to allow users to give semantic labels2 to different containers, and – ultimately – to use those labels to affect how the UI displays containers and their contents. I think part of the problem is that notebook ...


1

Hmm, the "reset password" screen should be a temporary, tokenized screen, divorced from any logged-in view. In other words, even if they're logged in on the device they open the "reset password" screen on, the screen they see should have nothing to do with that logged-in account. It doesn't need to log them out, necessarily (that's up to your dev team to ...


Only top voted, non community-wiki answers of a minimum length are eligible