Google mail...Google browser?
Written 21 Sep 2004
<p>At <a href="http://arstechnica.com">Arstechnica</a> this morning, they are <a href="http://arstechnica.com/news/posts/20040920-4206.html">reporting</a> (from the <a href="http://www.nypost.com/business/30438.htm">NY Post</a>) trends that suggest <a href="http://www.google.com">Google</a> maybe targeting browsers as their next foray. Apparently a number of people with browser building skills were recently hired, and the domain gbrowser is held by <a href="http://www.google.com">Google</a>. Ars asks "The larger question is one of why. Why a browser? What does <a href="http://www.google.com">Google</a> hope to offer that isn't already extant in the web browser market?"</p>
They answer it with the statement: The obvious answer is linkage to other Google properties. In other words, they are viewing it similar to the value of certain portals of years gone. However, there is potential for more. This harkens to the view of old: the browser as a platform. Google now holds many valuable Internet applications: webmail, adserving, search engine, blogging, and more. What if they were able to tie1 these with a "rich" client?
This interface could be done in several ways:
<ol>
<li>XUL</li>
<li>JavaScript & <abbr title="Document Object Model" alt="">DOM</abbr> parsing</li>
<li>A browser shell</li>
</ol>
<p>With such an interface, think of how much better, and easier to use, their Internet applications would be. And, of course, more possiblities open with such: more space for branding and adserving, better tie-ins for other <a href="http://www.google.com">Google</a> properties and partners.</p> <div style="font-size: smaller;"><a href="#foot1" name="foot1" id="foot1"><sup>1</sup></a>At least loosely. The tie-in could still allow regular browsers to use their properties, but with a more "limiting" experience.</div>