One, a few problems that entry interface often encounters

1, ” register ” ” look for a password ” wait for these a blame ” login ” of task itself own should arrange over?

My viewpoint: Must make clear above all ” they do not belong to strictly speaking this task ” .

It be put where is not important to be put where, important is we need to be behaved ” relevant task ” , do not regard as the main element of this task interface will handle. (no matter still be in in the framework,go up not to let him interactively ” a presumptuous guest usurps the host’s role ” )

2, ” save Cookies ” ” entry setting ” etc some ” login ” how should be the directly-related members of one’s family -parents of the task handled?

My viewpoint: Above all, these attribute the one part of the task.

Next, if acquiescent setting can be helped,finish these information to be able to not need to show in entry task as far as possible.

Next, if need must concise, but concise while the expression that should notice a character (be like, “Log onto = automatically to save a password land automatically ” expression is very improper) . And the equipment option setting that must note acquiesce.

3, is the permutation that expresses sheet horizontal setting of types or vertical setting of types? How should be horizontal setting of types discharged, how should be vertical setting of types discharged again?

My viewpoint: Horizontal setting of types or vertical setting of types should see the composing place of the page need, without the principle question with big what. Specific how does the platoon want to ponder over affirmation to know balance attentively only,

The focal track span of user of horizontal setting of types is bigger, but the space takes up lesser; The focal track of user of vertical setting of types can be linear, but the space is larger. If the condition allows me to suggest to use vertical setting of types, if normative place is restricted or the condition is finite I do not mind with horizontal setting of types. But I mind the behavior that in the acquiesce in inputting casing a few similar ” input the goofy clew information such as password ” again very much below major case.

4, whether to need yard of test and verify?

My viewpoint: If security does not have the word scarcely of big question,want.

But the moment of technical partner majority that is like you can tell you ” security ” have big problem, so a lot of moment we cannot ” indulgent for the good experience of detail safe be thwarted of the system ” . . .

Can so this proposition change simply ” is test and verify piled up ” how should design?

I object one: Chinese test and verify is piled up (the design of pure mental retardation)

I object 2: English and code of digital compound test and verify (to the user the input brought many troubles)

I object 3: More than 4 test and verify is piled up (be like in memory is what research result allegedly)

I object 4: Have yard of uppercase test and verify,

Especially big the ordinary form of a Chinese numeral mixes and big the ordinary form of a Chinese numeral still does not distinguish when effective system is judged — although you are not divisional big the ordinary form of a Chinese numeral, but what you show is a lot of users meet capitalization very laborious open great input to fill in uppercase, virtually brought a burden to the user.

2, the entry job design that I like is analysed one of

Bookmark:Digg Del.icio.us Reddit