I’ve been trying to examine the way apps “think for me” for quite a while. it seems like they usually have a good reason for deciding how to present data and help me with day-to-day tasks. But only when stripping common uses and REALLY thinking with a clean slate — new ideas come to mind. That was the case with my previous article about Google Calendar and as I promised there, I have some more thoughts and ideas using this “Clean Slate” methodology.

This time, staying in the field of productivity, I’ve decided to focus on Google Maps with a new way to think about navigational needs.

The Concept

Google Maps is excellent for navigation. Whether it’s my car, the bus or walking, it’s a great solution for getting from point A to point B. But when?

A great solution already exists within Google Maps: the possibility to plan your future navigational needs works perfectly (i.e. To arrive some place tomorrow, by bus, at a certain time. That’s super useful and really well thought of).

But what if the “when“ is a looser term? What if when=The best time for me. Bare with me on this one, as I explain my idea:

Best timing™

Best timing is based on information Google already knows, and it’s basically the best time for me (and you) to get somewhere.

The Problem

Let’s take Aaron as an example: