{"feed":"Recent-Questions-User-Experience-Stack-Exchange","feedTitle":"User Experience Stack Exchange","feedLink":"/feed/Recent-Questions-User-Experience-Stack-Exchange","catTitle":"Design","catLink":"/cat/design"}

What do you call a combobox in which what you write in the combobox filters a (long) list that can be accessed as a dropdown menu.

Here we filter with the strings igh, s, and not old; so any line that does not contain old but which contains igh and s in any order anywhere in the line is displayed in the list, and lines not containing both ighand s or old are ignored.

As UX Designers, we change and create words for things in the UI. Sometimes those are labels, sometimes error messages etc.

I've found it very difficult to keep documentation - say confluence up to date with the correct terms. I would love to be able to insert a token in the documentation that would change a specific term en masse - but I have no idea how this could be done.

This also extends to the UI itself - how have you changed words en masse in an efficient way?

We have one client and a subset of their users who struggle with Google's reCAPTCHA. They report issues of not being able to solve the challenges.

Our issue is we don't have that problem. Even when purposefully failing the challenge by selecting an incorrect tile or not selecting enough tiles, the challenge either submits correctly or informs us that we're missing a selection.

The captcha is applied to a payment form, and we don't want to remove it as this client has had issues with bots in the past.

Is there any other bot-thwarting system or practice that might solve this problem?

We used to utilize honeypots in the past but as autofill has become better, we've had to phase that out.

What is the best view for CRUD? Is it table or card view?

CRUD structure is

Name: XYZ
Date: dd/mm/yy
Query: location: a1,a2; State: s1,s2;etc

In my CRUD only editable field is Name. I can edit and update name. In addition to this there will be alert frequency (i.e whether i would like to receive it weekly, monthly or quarterly) in which user can select among multiple views and select the one which user is interested in.

I feel card view works out because my query can be very long. So I can give an option read more/less. Table view will look odd as some view's will long and some short.

I'm working on an analytics dashboard. Most of the data we get is pulled in from multiple sources/3rd party tools. Also, most of the data is user generated content so we don't have a control on what is being shown. Majority of the information displayed on the UI is dynamically displayed.

So the major problem I am facing is accommodating the long strings of data being displayed in various forms on our interface:

  1. Entity/brand names

  2. Menu items

  3. Entities on the graph scales

  4. Graph legends

  5. Cards view

  6. List view

  7. Drop downs

At some places we’ve used ellipses at the end and shown the full name/text as a tooltip on hover. However, I’ve received feedback that this is hampering the experience of the product since data is our USP.

We’ve tried wrapping the text to multiple lines at certain places but that results in compromising on the look & feel of the product. Example - size of cards will vary in a grid.

I want to standardise one behaviour across the product for any long text scenarios.

Can anyone give any ideas on best practices or solutions for this?

I am thinking on the following task:

I have a document with the content for the web-site. Document is structured with Level 1 headers. Under each header there is relevant content. One of the top level headers - "Services". Its' content has three Level 2 headers:

  • "For Startups",
  • "For Enterprise",
  • "For Venture Capital Investors".

Each of these Level 2 headers filled in with text.

The problem:

I want to avoid sub-menus. Only top-level menu that will include Level 1 headers from the content document. At the same time I want to show "For Startups", "For Enterprise", "For Investors" (at least these names) on the top of the "Services" page so the user will embrace that there are three kinds of services without scrolling down the page.

The question:

What are the known practices of achieving sub-menu effect without actually using sub-menus?

Reference web-page:

I'm expanding my app's capabilities from this: displaying all the rules that were applied, results for each rule, rule description, and link to more info.

I'd really appreciate pointers to apps which solve this kind of detail/detail display well. Here is how a couple of other apps solve this problem. I feel like there can be better ways to do it:

Edit: here's an interesting solution on

I work for a small startup, and I'm the sole UX designer, responsible for a couple of products. I also have the duty of ‘product owner’ managing the sprints and epics we tackle every two weeks. I’ve implemented a UX design process, that has been in place since the start that the stakeholders and team understand clearly. There is full transparency into this process, the documentation, the UI and the prototypes. For example if we have an idea, or we have an hypothesis. I research the idea. I make sure it aligns with our target audience (via persona’s). I build out scenarios and user flows. The I go to wireframes and/or prototyped and/or design - depending on the scope. For larger epics we do user testing.

The issue I’m having is with the expectation from a developer that the designs be 100% complete and accurate. I feel this is not reasonable given the size of the company we are, and the breadth of duties I (and all of us) have. I’ve worked with companies in the past, where if there were a gap in the design or UX, it’s brought up with myself or my team, and we provide the solution then and there. Problem solved, we all continue moving forward.

This is becoming frustrating - as it’s beginning to erode the teams moral a bit. For instance, when there is a QA bug or gap, which I identify, the usually response is “…it should have been in the design...

I have recently done work on this website Hidden Pearls. Basically the website was really broken from functionality point of view like its menu couldn't be even be open on mobile browser. It would just shut itself lol. I have now designed separate headers including menus for mobile and desktop. Their majority of customers are on mobile website. However I don't have much knowledge of UX stuff for E-commerce websites. If it helps, their target market are women in their 30s. Another thing that i have advised them to change is their All-Caps menu to lower case because of legibility. So if you experts could critique the website for any minor changes that could improve it from a UX perspective, that would be great! Thank you!!

How do I show two different summary text boxes side by side in a UI?

This is a screenshot from a screen I'm working on for a social justice app. This screen is meant to show messages from both the defence and the prosecuting counsel, but now the client has added that these messages could be up to 1000 characters, and this interface would break at that implementation. I currently need ideas on how this can be done. I would ideally prefer side by side since it's more of a comparism flow and putting one above the other might create some bias. But all solutions are welcome.

I'm designing an application with a bottom navigation, in one of the views, the user may click on a floating action button which opens a page containing a form to fill (this page (the form page I'm referring to) does not have the bottom navigation on it).

Is it confusing if I use a persistent bottom sheet on this page (as long as the user can add rows or attach something or other actions that are related to this form (as the persistent bottom sheets are "to display content equal in value to the primary content" as google states))

Of course the icons on bottom navigation and persistent bottom sheet are different, so it won't be a confusion due to similar icons.

Here's an example of what I'm trying to reach on the form page ( but it's on the web):

I'm designing a webapp that basically is patient tracking. We are in a claimant's "clip board" and it has all of the patients information. There are forms and there are some grids.

We currently cannot autosave.

This is an example of our health history screen. You can edit the grid, without being in edit mode. When you click the edit icon next to a field, you can edit that field.

When you press cancel, after you have edited a grid, do you expect changes to be lost in the grid and the form, only in the grid, or only in the form? See the example on YouTube.

Across the board, cars have shiny paint (which looks great), while computers, laptops and phones etc. tend to have a dull finish to them.

What’s the logic/psychology behind this?

Lately I've been spending a lot of time in the French speaking part of Switzerland. In being here I've noticed an awful lot of websites, including big names like paypal and google, breaking a major usability rule- try as I might to go to British paypal I often find myself redirected to a horrible Swiss German language version (most natives in this area don't even speak German!)

I've encountered this frequently in my time elsewhere, and it does seem to be somewhat in decline. But still redirects based upon IP addresses rather than user settings persist.

My question then: What possible justification is there to do this? I think its fair to say we all agree it is bad usability. But nothing in this world is black and white. What are the advantages of breaking this rule?- I have to believe paypal is not doing it out of pure idiocy.

In our app there are many pages of forms, and each page can have (or requires) photos attached to them. Photos can come from the camera, photos previously taken, or a view of certain photos from the iOS photo gallery. I don't have room for adding 3 buttons to each page so I want to make the photo functionality modal. Putting a UITabBar in a modal view seems odd (the app itself starts as a UITabBar). I could put three buttons at the bottom of the modal view and swap out the rest of the views with the camera (my own implementation not the SDK one) and the 2 galleries. Of course that is essentially a tab bar anyway. Any suggestions as to what might make the most sense?

This is what I am thinking of in the modal view. The page that would lead to this has a Photos button at the bottom plus other buttons for other features. Users are likely to take multiple photos or choose from the gallery while in this modal area. Note this is an enterprise app, not for the general public.

OF course this isn't a real UITabBarController.

Why are clients usually attracted to graphical user interfaces? Why aren't more applications developed using a console (command line / terminal) interface?

We are all familiar with the best password practices for websites which will be used by adults, such as storing passwords in one-way hashes, using password resets instead of emailing password, etc. But has there been any usability study regarding authentication systems in a classroom setting with young children? I wasn't able to find one with a quick search, but maybe I just don't know where to look.

The following are some considerations that need to be taken into account:

  1. It is commonly known that children forgot their password, especially younger ones. Is there any evidence that children forget their password more often than adults? How often do children forget their password?
  2. Usability is just as important as security. If a classroom is delayed because of password issues, then the system has failed. However, we do not want to be teaching children bad password practices either.
  3. We want to avoid burdening both teachers and students with a vicious cycle of children who keep forgetting their password because the teacher had to keep resetting it every week. This makes it tempting to save the password in plain-text/reversible encryption so teachers can just tell students their previous password instead of changing it, but is this really worth it?
  4. The site is used in a school setting, so when in a classroom, there will always be a teacher available to reset students' passwords as necessary. However, sometimes the student may need to access the site from their home computer.
  5. Not all children own an email address. While most...

We are creating a drawing application where users can add shapes to a canvas. They can cut/copy/paste via keyboard shortcut or context menu. For the context menu, it's pretty clear that the pasted objects appear at the context menu's click point. However, the keyboard shortcut has caused this discussion in our team.

There doesn't seem any sort of standard for pasting objects in drawing applications:

  • MS Paint always pastes to the top right corner of where you've scrolled to.
  • Photoshop/GIMP pastes to the center of where you've scrolled to/your selection.
  • Paint.NET seems to paste on top of the copied area when zoomed out. But, when the pasted area is not visible, it tries to position it near the copied area.
  • Some applications paste "offset" from the original location. Multiple repeated pastes continuously offset.
  • MS Word pastes offset the original shape and scrolls you back which is very annoying
  • We have an internal application that always pastes to where the mouse is.

We don't want to do what MS Word does and scroll you back to the original pasted area. It is terrible UX. Therefore, our options seem to be:

  1. Paste to the center of where you've scrolled.
  2. Paste to the top/right corner of where you've scrolled.
  3. Paste to where the original shapes were copied (but also where you've scrolled).
  4. Paste to where ever the mouse is. I'm against this one because I believe that's what the context menu paste is useful for. Also, what do you do if your mouse is off screen? The first time the users paste, it may...

There was a not so recent blog post about the ideal button size of touch screen control sizes (sorry there is no link, the website is now a spam trap) that was based on the study form the MIT touch lab that gives some measures of the size and sensitivity of the finger.

As the author of the blog pointed out, this ideal contact size is much larger than the suggested size for Windows and Apple devices that is in their design guides. I am wondering why there is such a difference, and whether it makes more sense to increase the size of controls on touch screen applications, or if this is not really a usability issue at all?

Also, it seems that many mobile websites and apps seem to completely ignore these principles. I am sure the screen size poses a limitation to how big the interface controls can be, so is this simply a trade-off between being able to fit in as much information versus how easy it is to interact with the control? It feels as if the stylus is not something that is in much use.

A similar question has been raised on the minimum/smallest size that you can get away with, but I would consider this to be a different question to what the optimum size should be, because the smallest size accommodates the minimum usability requirement, whereas the optimum size caters for the best usability requirement.

Original link of the blog (now spam trapped)...




| Submit |

When designing forms, do you customize the text in the submit button? In the registration example above, would you leave the submit button with the default "submit" text or would you choose an alternative?

  • Register
  • Join
  • OK
  • Go

On other forms such as login, purchasing, updating account, how do you choose the right submission action word? Or do you think it doesn't matter?