Commentary

Google Maps For Android Now Voice Powered

In the latest addition to the Android version of Google Maps for Mobile, users can now speak their search queries rather than typing them in. Google also made a bunch of other tweaks that make the overall experience better.

In the latest addition to the Android version of Google Maps for Mobile, users can now speak their search queries rather than typing them in. Google also made a bunch of other tweaks that make the overall experience better.Google's main search product has been voice-enabled for some time. Now, Google has given voice searching powers to its Maps for Mobile product -- at least for the Android platform.

Basically, when using Google Maps on Android, rather than typing in your search query (a.k.a., "123 Main Street, Anytown, USA"), you can speak the query instead. Google said its voice recognition engine currently understands English in American, Australian, and British accents.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Google has also added the ability to get public transit directions in over 250 cities. Google says, "If you're looking for the best route on foot, use walking directions to take advantage of pedestrian-only pathways and to avoid one-way restrictions."

Another tweak includes a minor bug fix to Latitude. Now, once you've selected "find me" feature, Latitude will continuously update your location live as long as the phone is turned on. Previously, it needed to be updated manually as the user changed locations.

Google says that this version of Maps for Mobile for Android will not automatically update. Instead, Google is encouraging users to manually re-download it from the Android Market.


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