Tag Info

New answers tagged

0

You could try out a mix between a dropdown and an auto-complete, searching for each part of the "location path" separately, starting with "City", thus the autocomplete will discard most of the possible results quickly, and then if the user has/wants to scroll, it will be just a bit. Some details: By default show all results. Apply to the results ...


1

If the percent of user looking on their city is so high I would set as default the user's location and a CTA next to it to choose "Other location". I think write the name of a city is faster than look for it in a list. For this, there are some interesting articles like: Redesigning the country selector which contain at the end a link to an advanced ...


0

Here's how I solved this in a similar app: When the default keyboard is presented, you also present a second subview above the keyboard with the buttons [1][2][3] etc. horizontally across the top row. Those buttons essentially act as a "faux" keyboard row that shows/hides with the keyboard. You can also bypass the default keyboard altogether and design your ...


1

I see both as possible solutions, though it depends more on your goal. If you're looking to drive better content and currently have people managing all content going in, then you have the opportunity to drive better content. You can do this by offering verification, which is like a status symbol to your users. This helps in three ways: The verified user is ...


1

EDIT: I realized that my answer is much like Stephen Keable's. Don't know how I missed his! Will you only have users from US and UK? I'm from Sweden and my address neither contain a province nor a state. If this is a webform you could do a geo IP detection to detect the country and then use this information to automatically change the form. If for some ...


0

Rather than using the Checkbox to decide, could you perhaps initially show just a country drop down. Which after selecting shows the other fields and appropriate labels for the selected country. Try this fiddle for an example You could even pre select the country option based on IP address (with ability to override). I would also recommend using drop ...


2

If the system can determine if the data is a Identity1 or Identity2, I recommend you to have only one field and only one submit button, and add a label (or placeholder) to explain that you can give a Identity1 or Identity2. For example, assume that Identity1 is a name and Identity2 is an address, you can have : More generally you can have something like ...


3

As I understand, the user knows what he’s searching. So the user has to deside if it’s a task-search or a user-search. If the system is able to decide whether the input is a task-number or a customer-number one field would be better because the user would not be forced to decide. In the case, that there are hits on customers and on tasks you could ask the ...


0

Can you first tell us on what grounds you decided what the future users of the interface with those search boxes will need? As you know, we are here to design for users, but you said that your team is more convinced by one or the other solution. I'm quite sure that you should test it with users of this specific industry. It's not a common scenario and we ...


0

Do both fields behave differently or are the exactly the same but the user will want to put in multiple search items? If the user just wants to add multiple search criteria you could use an input with that accepts multiple inputs like Select 2.



Top 50 recent answers are included