| |
| 2 October 2005 |
 |
Let’s say user typed 25. It can be the beginning of the phone number. It may be 25 minutes timer. Or perhaps it’s 25 dollars he wishes to convert in some european currency. Or some code he doesn’t want to forget.
User types 82. This could be not the numbers 82, but letters TA. May be the user tries to call his friend Taylor. Or is it’s the beginning of the message “take me fishing this weekend”. Or it’s a reminder to “take the trash out”. Or web-address tadalist.com. These options are limited and should be displayed right away. Their order can be fixed or frequency-of-usage based. read related... |
view all ideas  |
|
 |
|
 |
| |
| Although it is a nice way to think about tasks, I have to wonder just how intuitive it is. I think users are more accustomed to looking for the feature they need and then performing it, rather than having the features filtered as deemed needed. Since this list will be edited and features discarded as soon as a new character is entered (when applicable), the change is fairly rapid. This could be a huge source of confusion to power users, especially if the software assumed incorrectly (ie phone numbers). It would be interesting to found out... |
|
|
 |
 |
 |
|
| Siong Chin | May 14, 2007 10:33 AM |
| |
|
|
|
| |
| Smart UIs can are a good thing if well designed, and can help minimize number of key presses for a given operation, something that is very important in mobile/handset apps. But sometimes, "smartness" is not well designed, and they try to make too much, to the point that becomes an obstacle. It is important to keep it simple, always, KISS, and probably also have the option to enable/disable it. |
|
|
|
|
|
|
| C. Enrique Ortiz | March 08, 2006 08:53 AM |
| |
|
|
|
| |
| Beautiful beautiful beautiful! Thanks for sharing! |
|
|
|
|
|
|
| Sarah Lipman | March 07, 2006 20:16 PM |
| |
|
|
|
| |
thanks.
never really worked on a Mac ).
and I guess it could use autocompletion, but I don't see a lot of benefits. You don't have to type a function name like "calculator" (this is Qix approach). you just type 25+3 and get the result and obviously you don't need autocompletion for that. |
|
|
|
|
|
|
| Eugeniu Clim | March 01, 2006 15:21 PM |
| |
|
|
|
| |
Nice concept preview. But I really think that a direct one ( without the Tabs) is pretty good too.
A real application already does that for series 60 phones (and I think can really come integrated next releases )
http://www.zicorp.com/qixfunctions.htm
Excellent and inspiring site! I think I will follow you example and start mocking up my interface toughts!
keep the excelent work!
BR from Brazil
Marcelo Oliveira |
|
|
|
|
|
|
| Marcelo Oliveira | February 24, 2006 07:45 AM |
| |
|
|
|
| |
| Well, It seems fun. But why not let is work like IDE's auto-completion. In the mobile world, the hardest job is typing. Just like the Software programming. And besides Auto-Fuction reduction seems not a very very big deal. Because function is always the 1st thing we think in our mind, not the last one. |
|
|
|
|
|
|
| Tze-Chien Chu | February 23, 2006 18:42 PM |
| |
|
|
|
| |
| I really like this idea. Obviously someone uses quicksilver on their mac ;) |
|
|
|
|
|
|
| john Anthony Evans | February 21, 2006 15:40 PM |
| |
|
|
