New answers tagged

0

Use pagination by default and only switch to infinite scroll if Javascript is enabled. Consider that some users will have javascript disabled, and it'd be nice if your site worked for them too. Typically this is not the case when infinite scroll is the only option. However, you can make it work for everyone and just give the JS users a smoother ...


0

I think you need to work out all the different types of interactions and states that the element can have before you can decide on the best way to represent it, because you will need to take into account of what are some of the expected user behaviours, what the standard conventions are and whether you can cater for changes easily in the future. Just to ...


0

There are so many ways in which you can show an item is read. You can play with greying out, using green highlights, showing a 'read' label hovering over the thumbnail of the document, showing a green tick, etc. Here are some quick sketches - I think based on the user group you are targeting and the kind of data you have, adding slight gamification ...


2

Here's a quick sketch of something you can try: You can add multiple websites and hierarchies and make the location field specific to that combination of website and hierarchy. You can also individually close each field. I think it's important let users toggle between multiple combinations that you have, which could also be done easily in this ...


0

i would recommend using the parent dropdown as a way of adding new child entries. Then have a delete button for each child element (kind of like how you have it). Remove ALL borders of the child elements and the "Add another ***" buttons. Add some basic animation to the child entries when they appear, for some light flair. DO you have any live examples ...


2

Let's consider the user stories. User story 1. As a user, I would like to book an appointment. It seems like in this use case there is no place for confirmation. If I booked an appointment via your webapp my use story is fulfilled. Why sending confirmation email then? Let's consider another user story. User story 2 I want to make sure my appointment is ...


1

I see four possible ideas: Unordered list Since the frequencies really have no internal ordering of value to the user, and the only thing that matters is whether or not they will collide, I would suggest the following basic format: download bmml source – Wireframes created with Balsamiq Mockups While not so sexy, that would fulfill the real ...


0

In that have you tried mega-menu https://s-media-cache-ak0.pinimg.com/originals/3a/29/3d/3a293db3ac85d0facc63b3af77af2a33.jpg


3

The main problem with nested menus is that as UI objects they are somewhat feeble. Their task is to appear for a short period of time and disappear once user made a selection. From this perspective, asking user to select multilayered menus is an awful task as menus tend to disappear on a wrong move of the mouse. I think a better option is to make nested ...


0

For this case I suggest to make in-place editor, instead of a drawer and display a button on rollover to view details. Something like this:


3

The issue that you are facing is primarily caused by the fact that your QA team is expecting single-page application (SPA) behavior out of (what sounds like) a multi-page application (MPA) design. You are right to question altering the behavior of the back button because users have been taught to expect that if the page reloads as they "move forward" ...


17

From an UX perspective there's not doubt that you should always show the user the current state of the system, if not, users could think that their action was not really performed / recorded which can only derive in bad things. (users untrusting the system, getting mad, redoing actions then to discover they have duplicated data and have lost their time, ...


0

Nice design. I prefer the first one. Users usually read in a top-down manner, resembling a F shaped. Its easy to miss the content located on the left at a glance. The first design gives me the impression that my content is easily accessible without shifting my eyes too much. The third design looks a bit busy and heavy to me. Is there a reason why you have ...


0

I guess, it's tough to answer the generic use case without seeing a mockup, but for the particular use-case the following comes to mind: If you don't want the scrollbar in principle you will have to provide some explicit navigation for the users. They won't be pleased if they can't see how to scroll the list. The biggest enemy of any UX designer is an urge ...



Top 50 recent answers are included