Commentary

Stephen Wellman
 

Gmail As Designed By Microsoft

Since Thanksgiving is just around the corner, it's time for some holiday chestnuts. Here's one: What if Microsoft, and not Google, had designed Gmail? How would the application be different? Let's take a look.

Since Thanksgiving is just around the corner, it's time for some holiday chestnuts. Here's one: What if Microsoft, and not Google, had designed Gmail? How would the application be different? Let's take a look.Here is one blogger's take on Gmail by Microsoft:


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

First of all, we need to rebrand the application name to something longer. Let's call this Windows Live Gmail, and add some of the visual elements connected with Windows. Also, as in Hotmail, there needs to be less space for the e-mail subjects to make place for a reading pane, which is full of verbose explanatory help text.

Ouch. But, wait, it only gets better:

For another design iteration in our inbox, we will need to camouflage the checkboxes next to the messages by putting a mail icon on top of them. Also, we need to break up messages from conversation threads into their individual parts. Furthermore, this version of Gmail needs to change from context-aware text ads to context-unaware graphic banners, which we'll require to carry at least one clip art. Gmail currently has a chat box which I don't use and thus find annoying, so I think we can build on that and expand it to a more full-featured chat widget, replacing the labels box. We'll also adjust the spam filter slightly to show a couple of more bulk mails in the inbox.

And finally, the complete product, Windows Live Gmail. Here is some more light pre-Thanksgiving reading.


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