It is much easier than that. For instance to find "Mike Patch", just start typing "PA" and the name will be right on screen as one of your options. If your Android device does not have a physical keyboard, tap the Search key then start typing "PA". You can customize what search results you want to include.
But this points to a philosophical difference between webOS and Android. webOS thinks that you want to look at Mike Patch's photo. Android thinks you want to send a text, email, call, or
do something.
Let's say you stuck in construction traffic and want to text Mike Patch "Stuck in traffic but will be there in 20 minutes"
This simple text in webOS is 54 keystrokes:
1. When you turn on your webOS device, webOS thinks it is to look at the background picture.
2. Then when you type their name.
3. When you select their name, "Mike Patch", webOS thinks you want to look at their picture.
4. Then you choose to text them
5. Type the text message:"Stuck in traffic but will be there in 20 minutes"
6. Tap Send
In Android, instead of typing (and getting a ticket in 30 states)...
This simple text in Android is 2 keystrokes
1. When you turn on the Android device, it thinks you want to launch an app.
2. Long-press Search and say "Text Mike Patch Stuck in traffic but will be there in 20 minutes"
3. Tap Send
In two keystroke in webOS, you can find a contact. In two keystrokes in Android you sent the full text.
In this example Android saved you 98% of the keystrokes...and 100% of the ticket.
See the
Getting Started section on
Search and Voice Actions for much more on how to use and customize these features.