Commentary

Stephen Wellman
 

Has Someone Already Written A Google Android Mobile Application?

Forget the fact that there are no Android-powered mobile devices on the market -- and that it could be a year before we see any Android-based cell phones. It seems some eager developers have already written an application that runs on Android.

Forget the fact that there are no Android-powered mobile devices on the market -- and that it could be a year before we see any Android-based cell phones. It seems some eager developers have already written an application that runs on Android.At least that's what Valleywag claims. Here is a look at the rumor:


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But I'm told by a source that WhatsOpen has also written the first wireless app for Google's new Android operating system. (You may know Android better as the software behind the still-mythical Googlephone.)

And that's not all. There are screenshots too.

The startup supposedly building the first Android app, WhatsOpen.com, is a "amazing web & mobile based super search engine." The app supposedly "shows users nearby stored and their operating hours."

I do think it's interesting that this phantom-app is a location-enabled tool. Last week I pointed out that business users want more GPS and location on their smartphones. Location, and not standalone mobile search, could be the big battleground for the mobile Web in 2008. In my opinion this explains why Nokia paid so much money for Navteq.

As for this possible Android app, I wonder if WhatsOpen.com will launch it along with the Android SDK next week as a proof of concept. What do you think?


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