Tag Info

Hot answers tagged

9

I use the term 'conditional input' to indicate that there are elements within the form that is conditional to the input provided by the user. I think appending the term 'conditional' in front of a UI element suggests that they are triggered by a particular condition. Remember that it is not necessarily the entire form that changes, but just specific ...


7

For a bilingual search, do not detect the language, just search both and return results from both searches. E.g. when typing "ma" in the autocomplete search box, you could get: maçã (apple) ácer (maple) For multilingual, it wouldn't work that well, but if the search in the chosen language returns 0 hits, you could use a whole-word search in all languages ...


4

I don't think there is a different name for the form itself. The form is still a form - except that maybe it borders on becoming a survey! When you start creating the form you shouldn't need to decide whether you need a straight form or an 'adaptive form' - you should be able to decide at any point - and add or remove the logic at any time. You don't need ...


3

Not an easy question. 1. You can't let people click 5 years' worth of days. That will take ages. 2. Off the top of my head, a nice way to lower the amount of clicking: Perface the date picker with some thing like this download bmml source – Wireframes created with Balsamiq Mockups This will at least ensure the user doesn't have to click ...


2

Having built a few apps in a similar space many years ago, the underlying UI/app framework is unhelpful. Essentially what you have is both a "List UI" and "Item details" on the same screen. Two basic options: 1. Have two separate screens - List & Item Simplest to implement. Arguably could be less efficient. download bmml source – ...


2

Tabs usually contain different data. For example different sections of a form, like @staccato said. Now each tab is a new annex which the user add. When adding a lot of annexes it will be difficult to distinct different tabs. Instead of tabs you could have a list of annexes and a plus button below it. (For creating a new annex) You can have a list of ...


2

Usually I would have thought the fallback for signing with a signature is to enter the name. With that in mind you could simply ask the user to confirm with signature or name, with the default being the signature. Entering the name would be almost as good as a signature in as much as it's getting the user to accept responsibility by putting their name to ...


1

Break it up into multiple forms and present them to the user in several steps, see http://msdn.microsoft.com/en-us/library/windows/apps/xaml/jj839734.aspx You can process the answers after every step on the server-side and show different questions in the following steps based on what the user entered.


1

Current Password without a doubt. The typing clarification isn't necessary, and as general rule, if it doesn't make it better, discard it. Consider: That kind of form (password changing) is the same in almost every site. Also it's placed in the same section (edit profile, settings, etc). Inside a text input, specially a password input, to add the "Type ...


1

In marketing lingo, it's called qualifying question or filter question. I doubt there's a proper technical term, it's more like two things mixed up: that it's a form and that it's reactive / dynamic / conditional. But if you need a catchy name, how about responsive form? In a web based solution, a form would be done in HTML (<form>, <input>, ...


1

Decided to make UI much simpler and obvious, saved a lot of space in the process! :)


1

Enforcing one language on an element within a multilingual experience might be confusing. If your users are using several languages on the app, then that should be respected. Otherwise it could be mysterious why all of a sudden everything appears in English, for example. However, to eliminate confusion on the auto-suggest element, you could simply allow ...


1

Don't ask the user a question if you don't have to. Same answer essentially as @Aprillion but explicit rendering can help user e.g. download bmml source – Wireframes created with Balsamiq Mockups Will work OK with up to 3 languages - so default to English + users locale + (optionally) IP based locale


1

I understand that this is a data entry form for inserting and updating system entities into a database. Seems like a tool that people would need to work with on a daily basis and it's therefore imperative that the UI they use doesn't cause too much cognitive load, which results in unhappy users. The form you're presenting is over 20 fields long. I first ...


1

Why not have 3 separate drop-areas? You seem to have horizontal real-estate to make it work. download bmml source – Wireframes created with Balsamiq Mockups It would be a challenge to make the dialog balanced, as this heavy control at the bottom will draw a lot of attention. Possible solutions: Add more contrast at the top - brighter text, ...


1

You should experiment with various options and try which is the most intuitive to your users - you will likely need a Settings menu anyway so users will be able to choose 1st day of the week and so on... default status for the dates could be undecided, default action of 1 click could be to make the day available, 2nd click would toggle it to unavailable ...


1

First of all: I understand you're under pressure and under some limitation. I will try to offer some improvements, but this is not the best solution, and might be problematic. Try to make the best of this by Monday, but try to get another timeframe for improvements. Suggestion: If you must view, edit and add on the same UI, tread carefully. You're ...


1

I think you're on to something. I would say that handling it server-side only and not alerting the user would be an acceptable way of handling it. However, some sort of feedback could be useful and personal as long as they don't feel penalized. One option is to tailor your submission response to be a generic catch-all. For example, it could just say "You're ...


1

You should never limit it, unless you have a very good reason. The users can sometimes innovate in unsuspected ways (it is said that tea bags where for test, and the consumers began to ask it in that way). Comments: A big NO, unless your system has some very strange use. You could wanna talk about a Greek person (say Socrates: Σωκράτης) in Spanish ...


1

Currently you hide a huge content from users, but it's a critical point for your service. Using multi-language makes the case even worse. For Google it works, but they have strong back-end for doing this. I suggest explicit presentation of the content, using multi-level selection. So you build strong information architecture of your content, which has the ...


1

If the type of some fields depends on previous choices/answers you can populate the form accordingly (= based on previous choices) using a framework like jQuery of plain old JavaScript. But if I understand it correctly the only elements in the form are 20 fields? If so, you could try grouping similar fields and use -for example- collapsible divs? So users ...


1

Another option is to use the list view, but provide a add icon for each list entry so user doesnt have to tap on the menu btn. You can tap as many times to increment qty or disable add if only one unit can be added at a time. Have a search icon in toolbar (top or bottom) to search for an item. For new users and even generally i think "list of items" is ...



Only top voted, non community-wiki answers of a minimum length are eligible