My colleague and I were talking earlier about whether to use the word
'hide' or 'collapse' for showing the simplified version of an object
on a web page. The object has three states: edit, preview, and
collapsed. We talked about using "twist-downs," as suggested in the
Closable Panels section in Designing Interfaces (Jennifer Tidwell),
but because we have three states, this doesn't really work.
I am having trouble determining if there is a standard or best
practice for marking which fields are required on a desktop
application form. This is a fairly standard Windows UI with lots of
dialogs. Each dialog has some mandatory and some optional fields, and
which are which tends to change with the data, system parameters, etc.
Therefore, I want to have some visual treatment so users can know at a
glance what fields are mandatory.
I'm looking for advice on localizing address fields. I'm designing a UI that
could potentially be used by folks in a large number of countries. The
target user profile is a small business owner who uses a computer to get her
job done, but is not technically savvy.
Different countries use different terms to represent similar information.
For example, the U.S. uses "zip code", but all other countries seem to use
"postal code." Similarly, the U.S.
Basically, I deal with a user task which frequency is low, but very
important to configure and updating the system. This task includes two
1--> a multiple selection in a large set (>50) where the average
selection number is 5 to 15 items. Each items have some meta-data that
can be useful to the user to make its choice.
2--> a multiple selection a a small set (<10) when the average selection
number 1 to 3.
For an average office worker or a businessman, what would be a top website
or a product that's so associated with its brand that if we were to blank
out the identifying logos and other marks, our sample audience would readily
I'm working on a touchscreen UI application at the moment, and as many
of you know, such interfaces present pretty interesting challenges.
This project is especially interesting in its complexity; it deals with
pretty vertical domain knowledge and its users need extremely flexible
and freeform methods of interaction with the kiosk...tons of buttons,
which certainly creates rather interesting issues of screen real estate
at 1024x768. ;-)
Naturally, this had made me very aware of touchscreen UI's I've used