Google Tips
google.com
google.com
https://www.google.com/get/googletips/card/ask-google-to-fet...
Which I had no idea about.
This is a brilliant content and feature discovery tool. Any other company would've just created a long list of products with short descriptions for each.
I wonder if it'll work.
Most of these fall into a few categories:
1. Hey, this service exists (Google Contacts, Google Keep, Google News) 2. Look at this intermediate-level thing you can do with this service (Install apps from the web interface of the Play store, make playlists on YouTube, natural language semantic Google search) 3. Bad UX (hey, you can share map search results!)
Google has a lot of services (leading to #1); a lot of users are very cautious about using computers in general and won't try to explore to find intermediate or advanced usages (even though they're very useful and HN would probably bitterly complain about their being taken out); the UX is sometimes bad but having user education doesn't automatically imply that.
Have we really gotten so addicted to onboarding that any feature that can't be explained in a 30-second "welcome to Google" tour should just be shafted? I really like being able to install Android apps from my laptop, but even if I was told that in the Android "welcome to Android" screen that I first saw years ago and haven't seen since, I'd have forgotten it.
Using any tool as an expert requires some amount of education. Is it really desirable to build tools that cannot be used as an expert? What would the world be like if the only tools that existed were only usable at the beginner level?
This reminds me heavily of the IFTTT recipes (https://ifttt.com/recipes). Google has so many parts that sometimes you need a little guidance to see how they fit together in a useful way.
Or by "this" did you mean Tips -- i.e. is your argument that you shouldn't ask your users for discoverability advice? If so, I can see how doing so requires a bit of indifference to embarrassment, and a lack of care as to what snobs might think, but hey, discoverability is hard.
How would you design a way to teach users they can do queries like this?
Try this: Go to Google.com as a logged in user and try to "switch" to your new account. What was originally one click to logout and one click to bring up a un/pw now takes a ton of additional user interaction.
I'm no Jony Ive but whoever thought this was a good workflow needs to reconsider.
I tried to "switch" to my new account, as you described. It took about 10 seconds, which was the time it took to load a new page and type out my credentials. Furthermore, as soon as I did that, I could instantly switch between accounts with two clicks and without having to log out of either account. What's the problem?
Google is on a real push lately to get people to stay signed into its services all the time. This, to me, feels like another pair of hands helping in that push.
[0]http://productforums.google.com/forum/#!topic/calendar/SJZxi... [0]