Taskfox/Name: Difference between revisions

Taskfox/Name (view source)

Revision as of 01:09, 19 March 2009

1,427 bytes added , 19 March 2009

m

→‎Introduction

Indolering

501

edits

@@ Line 2: / Line 2: @@
 "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.
+: 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.
+: 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.
+Avoid broad names for specific features
+# Make sure the name works well in a short sentence describing the feature.  Examples:
+-"spotlight helps you find things on your computer"
+-"automator helps you automate tasks"
+-"time machine helps you recover after a crash"
+-"private browsing lets you browse the Web privately"
+Avoid common Microsoft modifiers
+Name the feature early in order to get the name to stick (smart bookmarks vs. microsummaries)
 == Name ==