Commentary

Stephen Wellman
 

Google And Dodgeball: What Went Wrong?

Mike Masnick at Techdirt is curious why Google's acquisition of Dodgeball has yet to produce anything. I have to agree with him. What happened?

Mike Masnick at Techdirt is curious why Google's acquisition of Dodgeball has yet to produce anything. I have to agree with him. What happened?The issues surrounding Dodgeball are even more interesting given just how much Google has been talking about mobility in recent months. Just this week, Google CEO Eric Schmidt was talking about both wireless and local search at Web 2.0.

But Schmidt's comments are especially ironic given, as Mike pointed out in his post, that Dodgeball's founders very publicly dissed Google and quit their jobs.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Google obviously sees its future in wireless, yet Google has yet to do anything interesting with SMS-social networking service Dodgeball, one of the most promising early Mobile 2.0 startups.

Some Web insiders are beginning to think that Google may not be so good at integrating startups. Certainly the YouTube acquisition hasn't panned out all that well. And Google has acquired a lot more startups than Dodgeball, and we haven't heard much from most of them, either.

In fact, Google may now be to Web 2.0 startups what Microsoft was to software startups in the 1990s.

On the other hand, Google may be using Dodgeball's technology to develop new applications we don't know about. What do you think? Did Google just mess up the integration of Dodgeball? Or did it buy the company just for the technology with no real plans to grow the product?


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