Commentary

Stephen Wellman
 

What If Mobile Search Doesn't Use Text Input?

Everyone knows that Google is prepared to conquer the mobile Web. Prompting all these initiatives is Google's drive to dominate the mobile search and ad markets. I have one issue with Google's strategy: It assumes that mobile search will operate like desktop search, using text input. What happens if mobile search doesn't work the same way as search on the desktop?

Everyone knows that Google is prepared to conquer the mobile Web. Prompting all these initiatives is Google's drive to dominate the mobile search and ad markets. I have one issue with Google's strategy: It assumes that mobile search will operate like desktop search, using text input. What happens if mobile search doesn't work the same way as search on the desktop?The answer is simple: If mobile search takes a different path, Google is going to need to rethink its strategy.

Despite the apparent innovation with Android and its other efforts (like its push for open network access), Google's core mobile offerings -- text-based search with a mobile version of AdWords -- are just a replica of its desktop products. What is so innovative about this?


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Google seems to think that mobile search will operate similarly to desktop search. But the fact is, mobile search is already quite different than desktop search. And, frankly, mobile search isn't easy to use and it doesn't work that well.

In order for the mobile search market to grow, it needs to work. And for that to happen, mobile search needs to be easier to use. I think mobile search needs two things it currently lacks. The first is location and GPS. Mobile searchers need to find items and services fast, and they need those items to be close to them. They don't need 20,000 results, they need two or three, and those two or three results need to be hyper-relevant and geographically close. While Google's mobile search does cut back the number of results of a typical desktop search, it still offers way too many results and those results aren't sufficiently relevant or proximate.

Mobile search also needs an alternative to text. Sure, text input is great on the desktop, but it's cumbersome on mobile devices, even smartphones with qwerty keyboards. Don't believe me? Try typing out those 1,500 word business memos on your BlackBerry. You can do it -- trust me, I have written some long e-mails on smartphones before -- but if you give me the choice, I will always use a notebook or desktop keyboard before a qwerty keyboard to type longer messages. Why is mobile search any different? If you're good at using Google, you frequently type longer, compound queries. But that's often not feasible on mobile phones.

I'm not sure what the alternative to text input will be, but I think Nokia's Point&Find application could offer a glimpse of nontext mobile search input. Why not use images from camera phones to power mobile searches? Image processing combined with GPS could offer a simple point-and-click search mechanism that's far easier to use than existing mobile search systems -- and more useful, too. But such a different search system might not monetize the same way as Google's desktop search. This is a reason for Google not to pursue this approach. But it's definitely a good reason for Google's rivals, such as Nokia, Yahoo, and Microsoft, to look at it.

What do you think? Will mobile search evolve away from text input?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links