Skip to main content

Why Did Google Decide To Split Inbox From Gmail?


A couple of years ago, right around the time Google’s Gmail team decided to start working on a standalone email app — the recently announced Inbox — a major redesign of Gmail was launched. As is the case with all Google products it was first released internally as “dogfood” to let Googlers themselves digest all the new features, or as was the case with this particular redesign, the removal of most of the advanced features.

The Gmail team did not have to wait for the reaction for long. And it wasn’t very “googly.” It caused an uproar teeming with disgust for just about every decision the Gmail product/design team made. Phrases like, “You guys just completely destroyed Gmail!” and “What are these crazy designers doing over there?!” were everywhere. From being spoken at many of Google’s cafes to every internal online forum.

Google engineers, in typical OCD engineer fashion, wrote long internal Google+ and forum posts detailing every single use case that was no longer supported, no matter how obscure. Hell hath no fury like a product team removing a feature an engineer had been using on a daily basis. Add to that the decision to turn words into icons and add white space between rows and Google engineers were ready to storm the Gmail product/design team office with torches, swords and in full knight armor (you’d be surprised how many Google engineers own that stuff).

In response, the head of the Gmail design team made a presentation entitled “You Are Not the User.” If you were not lucky enough to witness the carnage in person you could view its archived version on the internal Google+.

The presentation detailed the reasons behind every decision the design/product team made showing gobs of usability data supporting the decisions to remove advanced features that the overwhelming majority of Gmail users were never using. These features, it was argued, were unnecessarily complicating the user interface when most people just wanted a simple email client.

All of the decisions revolved around the central fact that a typical Gmail user was receiving only about five emails per day, most of which were of promotional nature, and as such, required no response. This was in contrast to a typical Googler who received an average of about 450 emails per day, many of which were important to at least read, with a good chunk of them requiring a reply.

Despite supplying a large amount of concrete data supporting the Gmail design/product team’s decisions the presentation did not quell the criticism, but rather stoked the fire even more. Even its title was called “purposefully inflammatory” and further upset Googlers who, like many techies, were using every possible advanced feature to deal with the daily onslaught of email.

Finally, a compromise was reached. Gmail would stay streamlined and optimized for its gigantic user base (hundreds of millions of monthly active users) while still keeping some of the more advanced features (now well hidden) for those who really needed them.

In parallel, the Gmail team would begin working on a standalone product specifically designed from the ground up for advanced users who have to handle a firehose of incoming emails every day. And that’s how Inbox was born.

Source

Popular posts from this blog

How To Hide Text In Microsoft Word 2007, Reveal It & Protect It

Sometimes what we hide is more important than what we reveal. Especially, documents with sensitive information, some things are supposed to be ‘for some eyes only’. Such scenarios are quite common, even for the more un-secretive among us. You want to show someone a letter composed in MS Word, but want to keep some of the content private; or it’s an official letter with some part of it having critical data. As important as these two are, the most common use could involve a normal printing job. Many a time we have to print different versions of a document, one copy for one set of eyes and others for other sets. Rather than creating multiple copies and therefore multiple printing jobs, what if we could just do it from the same document?  That too, without the hassle of repeated cut and paste. We can, with a simple feature in MS Word – it’s just called Hidden and let me show you how to use it to hide text in Microsoft Word 2007. It’s a simple single click process. Open the document

Clip & Convert Your Video Faster With Quicktime X & The New Handbrake 64-bit [Mac]

Recently a friend of mine asked for my help to find a video of a good presentation to be shown to one of his classes. He also requested for it to be iPod friendly as he would also distribute the video to his students. Three things came to my mind: Steve Jobs, Quicktime and Handbrake . Mr. Jobs is well known for his great presentations which are often used as references. I have several Apple Keynotes videos. For my friend, I decided to choose the one that introduced MacBook Air – the one that never fails to deliver the wow effect to the non-techie audience. It’s a part of January 2008 Macworld Keynote. First step: The Cutting To get only a specific part of the Keynote, I clipped the 1+ hour video into about 20 minutes using Quicktime X (which comes with Snow Leopard). I opened the movie using Quicktime X and chose Trim from the Edit menu ( Command + T ). Then I chose the start and end of my clip by moving both edges of the trimming bar to the desired position. To increase th

Ex-Skypers Launch Virtual Whiteboard Deekit

Although seriously long in the tooth and being disrupted by a plethora of startups, for many years Skype has existed as an almost ubiquitous app in any remote team’s toolkit. So it seems apt that a new startup founded by a team of ex-Skype employees is set to tackle another aspect of online collaboration. Deekit, which exits private beta today, is a virtual and collaborative whiteboard to help remote teams work smarter. The Tallinn, Estonia-based startup is headed up by founder and CEO, Kaili Kleemeier, who was previously a Head of Operations at Skype. She and three colleagues quit the Internet calling giant in 2012 and spent a year researching ideas in the remote team space. They ended up focusing on creating a new virtual whiteboard, born out of Kleemeier’s experience collaborating with technical teams remotely, specifically helping Skype deal with incident management. “Working with remote teams has been a challenge in many ways – cultural differences, language differences, a