501
edits
Indolering (talk | contribs) m (→Introduction) |
Indolering (talk | contribs) m (→Introduction) |
||
| Line 3: | Line 3: | ||
"Taskfox" is a codename. Don't expect Firefox to ship using this name. This page is a list of suggested names, thoughts on names, and general terminology. Feel free to add to it. | "Taskfox" is a codename. Don't expect Firefox to ship using this name. This page is a list of suggested names, thoughts on names, and general terminology. Feel free to add to it. | ||
Do not remind novice users of the hell that was DOS. | # Do not remind novice users of the hell that was DOS. | ||
: This includes the use of “command line interface” and all buzzwords such as [http://www.viddler.com/explore/indolering/videos/17/840 mashup], dashboard, and even [[labs/Ubiquity/Usability/Usability Testing/Fall 08 1.2 Tests#Analyzing_Data|hotkey]]. | :: This includes the use of “command line interface” and all buzzwords such as [http://www.viddler.com/explore/indolering/videos/17/840 mashup], dashboard, and even [[labs/Ubiquity/Usability/Usability Testing/Fall 08 1.2 Tests#Analyzing_Data|hotkey]]. | ||
Do not give the impression of a natural language parser, otherwise users go overboard or send mean vibes. | # Do not give the impression of a natural language parser, otherwise users go overboard or send mean vibes. | ||
: All current successful natural language AI’s bring with them a set of expectations that users respect. For example, people have been trained to carefully enunciate with telephone systems (Apple’s support line is great one). [http://www.gametrailers.com/player/usermovies/272933.html Video games] and telephone systems also structure the interaction in a multiple choice format to restrict the universe of possibilities that users will throw at it. | :: All current successful natural language AI’s bring with them a set of expectations that users respect. For example, people have been trained to carefully enunciate with telephone systems (Apple’s support line is great one). [http://www.gametrailers.com/player/usermovies/272933.html Video games] and telephone systems also structure the interaction in a multiple choice format to restrict the universe of possibilities that users will throw at it. | ||
Give clear clues as to what Ubiquity is useful for and leave an impression that it’s of easy to use. | # Give clear clues as to what Ubiquity is useful for and leave an impression that it’s of easy to use. | ||
Avoid broad names for specific features | # Avoid broad names for specific features | ||
# Make sure the name works well in a short sentence describing the feature. Examples: | # Make sure the name works well in a short sentence describing the feature. Examples: | ||
| Line 21: | Line 21: | ||
Avoid common Microsoft modifiers | # Avoid common Microsoft modifiers (Smart, live, etc) | ||
Name the feature early in order to get the name to stick (smart bookmarks vs. microsummaries) | # Name the feature early in order to get the name to stick (smart bookmarks vs. microsummaries) | ||
== Name == | == Name == | ||
edits