New answers tagged

0

As an alternative to Mervin's excellent answer - there are cases when between tabs if there is too much content then it makes sense to load the tabs as you click on them. However for the reasons Mervin gives, I'd suggest that AJAX loading still wouldn't be the way to go, unless you're writing a single page app. Here on UX.SE, the different views between ...


2

Your second option is the best. Follow what WooCommerce do, they have one of the largest sets of options of any plugin, and they group them logically, not caring if one tab just has one option: Tab contents for usability need to be grouped logically. The label at the top needs to be able to succinctly describe what will be laid out in that tab. From ...


2

Here is an option i think will be great (experimental): Divide all the controls in two groups, common and rare use. Show only the common controls on one page, and add at the bottom an input field that will will ask the user if he needs something else. The user will enter a search query in a natural language: "I want to change the permissions for guest ...


0

This is one of the best example for snappy UI. But, there is risk involved with this approach. In general user tend not to wait for more than half a second for navigation. With this mental model, expanding a tab and activating contextual buttons/actions should be handled carefully. This could be effectively achieved by distinct visual design, ...


1

I wouldn't advise doing that. User usually perceive an expanded list of options to be a drop down menu. Sideways menu might throw them off. Implementation could be challenging too especially if your app needs to be responsive. You probably have to be extra careful when you placed additional components beside the 3 buttons.


0

Tabs are usually used to divide a large content into sections and then alternate its views within the same context. Nielsen Norman Group has a very good article on its proper usage. They are usually placed next to each other (without spacing) to form a single component. The reason for this UI pattern is to let user know that the information the individual ...



Top 50 recent answers are included