Indicate which tabs have errors, and show the errors for each section within the tab.
Optionally, if you find it suits your use case and how users interact with these tabs, you could include a summary of all the errors. Providing an overall summary of errors could be useful if the tabs are dependent on each other, or if the data is interconnected.
Honest answer is - It depends on the amount of information, how you want your users to see the information and width-height of the interface
I was writing in details, but I'd rather choose this answer which can give you a clear idea in details, and the answer is much more informative.
accordions vs tabs
I think most of the business websites and big social websites use an email instead of the username, but in your case try to do not confuse the user, you can just place over the username field Email/Username, and your system must apply some simple methods of AI to detect the username field content, for example:
If you start typing something in the username ...
Ask yourself: Do users need to see all content in one page or at a glance? Do the tabs represent categories?
Tabs (Used to ease navigation and group related content):
Are you categorizing or logically grouping the content?
Are you trying to discourage vertical scrolling in case there is a lot of content vertically displayed?
No Tabs (It is better to ...
First solution is vertical scroll, often used on mobile. With placing arrows right, and when needed left..
Second solution is having "toogle more" button on end, where you toggle all other tabs that didnt fit.
Thirds solution is "mega drop down", as you maybe can think that tabs are not best solution if you have so many items.
Although the usual norm for a dashboard is to keep a viewable height, they can be made to scroll vertically as what happens in Google Analytics and a lot of other analytics pages. Instead of creating multiple tabs, it is best to try to sort multiple of them in a single long scroll page particularly useful when the same filter is applicable, makes it easier ...
I am not sure how log you can allow user to add new tabs, and also not sure if tabs can be combined into one group like,
- Group 1 -> Tab1 , Tab2, Tab3
- Group 2 -> Tab4
- Group 3 -> Tab7, Tab8 and so on
Then like menu hierarchy we can give UI which would be more simpler to user to access each section.
If Not then there are more other two ...
I think the problem comes because you're mixing READING and EDITING screens. If you're editing, you need to make it very clear. Your action buttons (please do not confuse with CTA) make sense on an edition page, but of course, they're not needed if the user is viewing data.
This is why you're facing this problem: in one screen you have nothing to save, ...
There are several different possibilities to place the dashboards. The most suitable control may vary depending on the context.
Carousel tabs: Allow you to quickly switch between 2-3 options, other options are hidden. In general, tabs keep the options visible at all times which makes it quick and easy to switch between options. On the other hand the take up ...
If I understood your question correctly, you are talking about nested tab bars, right?
Have you considered placing the main navigation into a sidebar on the left side of the screen? This way, you end up with a menu, that is commonly used and known by users, and also accomplish a clear distinction between your main navigation and your lower-level tabs.
Nothing wrong with tabs
There is nothing wrong with two sets of tabs. Tabs are a commonly used pattern and mostly well understood by people, using something unusual and new might leave users more confused.
From your sketch it looks like you maintain a clear hierarchy, as long as that is maintained in the visual design it should work fine (assuming it's a ...
By 'dummy tab' you mean placing that link directly onto the surface, in lieu of a tab? Yes, that is preferable to my mind. It presents crisper, more direct navigation: Your link doesn't need to be discovered beneath a tab that presumably has to hint at the presence of a link, which is superfluous... unless your hyperlink is extremely long and for some reason ...
You could have tabs, and have the external link off to the side:
This way you can keep the name as the general content type (but not make them click a tab just for a link), and show them the URL (and the concept/functionality) they're going to get:
My guess is it would have to do with usability.
In the case of the apps using top navigation bar (which, by the way, is also a recommended navigation pattern for Android Apps), usability may be better off by having the "lesser used" actions far away from the user's thumb. By doing this, they free up the space for users to swipe or choose any of the more ...
Is it possible to combine the fields into one input, and figure out which they used server side? That way, you can eliminate half the fields, and the user doesn't have to make a decision or remember whether they login with their email or username.