Treo 650 first impressions, Part I

[Archived in Entry]

 [figby.com - Michael Moncur's weblog] I played with one at the SprintPCS store and was surprised to find that I could type with reasonable accuracy despite this. It turns out that the Treo’s software is designed to watch for and correct multiple keypresses, compensating for my clumsiness nearly 100%. I can already get data into this device about twice as fast as I could with the Fitaly keyboard on my old Palm, and don’t even ask me about Graffiti. I’ve found that I almost never use the stylus—between the keyboard and the five-way navigator, I can do just about everything without it.

Some slightly related:

[Writing On Your Palm] PalmOne Tungsten T5 Review: The blue highlight that shows you which part of the UI has the focus of the D-pad (a really nice feature for one-handed navigation) doesn't always disappear when it should. When I've got the system loaded to the gills with background processes (Fonts4OS5 and FontSmoother loaded, playing an MP3 with PocketTunes in the background, using pToolSet to augment the system find, clipboard and other stuff, ShortCut5 to use shortcuts my keyboard can type, probably a few more I've forgotten about), things can bog down. This is the first device that I've actually seen pFindTool disappear and fill in the actual Find dialog character by character. Sometimes ShortCut5 will "type" the expanded text slower than I could have with Graffiti.

Posted at May 13, 2005 09:28 AM | Comments (0) | TrackBack (0)