New answers tagged

1

From my point of view, changing switch button doesn't make it more understandable. If you are going to change it anyway other than a slider, I'd prefer something meant two-sided image/emoji (like gemini) to make it more understandable as it's a changeable item. And as you say so, putting your name next to this slider icon, does make this icon more like your ...


2

I also prefer the bottom one, with the lighter navbar. There's more contrast, both for the bar itself and for its shadow. As for consistency, you could think of the dark theme as generally inverting all the colors, which also flips the relationships, like what happened here.


0

Remember that all software has the same purpose to make life easier for people... In software design, friction is basically anything that makes your users think, wonder or question. Reducing friction is key to making life easier for people. see: Don't Make Me Think Your colleagues are correct in that doing 1 of 6 things differently increases friction. ...


0

I got two options in my mind for this design problem where you can show all the available features 1) Overlay view 2) show bottom sheet https://www.figma.com/proto/rMftMLx9Ih3RRKtVVBrm6W/Multiple-options?node-id=1%3A70&scaling=min-zoom Please checkout this prototype for both options!


1

If I understand your questions correctly you would like to add more navigation menu items, on the bottom navigation bar in your app, than is possible (visual). What we did in a concept was: - Show 4 (most used) items in the bottom navigation bar - The fifth item was a hamburger or submenu (the 3 dots) with the title 'More' on the most right side of the ...


0

Even if you would have a few tools. ( let's say 5 tools ) it would still be good to allow the users to jump directly to one of them. I don't really know what the calculator is for in your example but have it like this. I know your website has a calculator and I would like to reach it. Why would you make me click the main menu to access a submenu that takes ...


0

I think this shouldn't be an issue. Beta testing should always be done by invitation and controlled as much as possible. As such, it should NEVER have a link to the existing site. You need to make sure your users will test the beta version and nothing else, and they need to be aware that the version is a beta one. If you don't do this, the amount of ...


1

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 ...


0

Hmm, it depends how much information the widget will present, but using one in 100% is a lot of space: You can use that type of controls, for give opportunity to user to select, displaying the list as it suits him. As of Tabs - according to material design, so the practice you have used is not necessarily appropriate in this system design:


0

Standard hamburger icon for menu should do. And for closing it, "X" icon seems more appropriate than this chevron up icon you have now. Otherwise this you have seems good


1

Remember always, as a principle, that we (as dev) should try to prevent user errors as much as possible. You are talking about a form that is filled in 3 steps. If you are worried about usability, you should consider the following: Users should know where they are at all times, meaning that it should be very clear to them that they are in step 1, 2, or 3. ...


1

A good way would be to create checkers beside each information that the users would input. Let's say the user has to input four different information in screen A, then there would be four different checkmarks beside each info that lets the user know whether the input is valid or not. That way the user doesn't have to make the mistake first then have to go ...


0

Much has been said about the topic of predictability and discover ability. When we try solving a discover ability problem - which should understand, is it making something the user knows exist or things should be there available (Predictability), or is it about making the user aware of a feature, they are not aware exists. In you questions you are asking ...


Top 50 recent answers are included