Tag Info

New answers tagged

0

The clear distinction between "slider" and "carousel" lies on the user experience that both deliver, which define the context of both words: 1) Slide --> a knob or lever that is moved horizontally or vertically to control a variable. 2) Carousel --> a merry-go-round. Personally, I would opt to address, articulate and deliver them "distinctively"! I would ...


0

You can also refer to this link, http://www.usability.gov/how-to-and-tools/methods/user-interface-elements.html


1

A "View" is a single display unit. This entire web page is a single view. If you open up an app, that entire page is a view. You may have other views that are easy to reach, but what you see (with scrolling) on a single page is the view. For web, it's simpler, obviously. Links typically distinguish between various "views", which are individual web pages. ...


0

What's a File Extension? From a user point of view "file extension" is troublesome. Extensions can be hidden and often times are by default by modern file browsers. For many common file types, it doesn't matter to the user. For example, I don't care if the extension is ".doc" or ".docx" -- all I care about it that the file opens in Word, lets me modify ...


0

The issue is that the user doesn't know if the entry is acceptable or not until commiting the entry. This is bad. I can think of two solutions. Instead of a text box, have checkboxes with the possible extensions listed. This way, the user doesn't need to guess if the period is required or not (and it may be faster to check boxes than to type the ...


1

Part One You Do! Simply: If you need the information, it's required. If you don't need, but want it, it's optional. Part Two The Database Does! I like this better, in terms of the back-end. If your database has it as NOT NULL, mark it as required. If your database has it as NULL, you leave it as is and take what you get from the user. ...


0

Here's how I think of it: a "required" field needs a value in order for the form to be submitted. So, even if a field is pre-populated, I'd still mark it as required. (Consider address forms that pre-populate with the address info saved in your profile.) Now, whether you should pre-populate your Family Status field is another matter...


3

Given you’re designing the user interface, not the program’s interface, it makes sense to signal what’s required of the user, not what’s required of the program. Part of the purpose of the UI is to communicate the actions the user can or must make. In the case of require fields, the commonly used red asterisk communicates to the user “you must put something ...


4

In About Face it is suggested that the average user does not understand boolean logic. That's because in common language AND and OR have different meaning than they have in boolean algebra. For example, if I want all users whose age equals 15 or 30, I could say: "give me all users whose age is 15 and 30." It's pretty clear to a programmer that that and is ...


2

There's rather a lot in this article - and it's rather heavy going psychology: but the bottom line is that most people are rather rubbish at formal logic and deductive and inductive thinking: It's based on experiments called the 'Wason Verification Task' ...


1

we use "interact" example: button.on("interact", function () { ... })


3

They are different terms Callout is an older term that dates to paper-based design before the web. Callouts are used in design to draw attention to or label something. Here are some callouts labeling the orientation of a part: There are many ways to style callouts, but usually there is a line or an arrow to indicate the subject of the callout. Here ...



Top 50 recent answers are included