Now? not necessarily.
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:
Aaron is a 35 y.o. Interior Designer. He is a Freelancer with a large amount of clients from all around his city and its area. Aaron also works part-time as an illustrator for a small architects office.
He drives around a lot between his clients’ residence and various supply stores. Twice a week, he commutes by bus to his part-time job at the other side of town.
Aaron needs to get to IKEA. He needs to purchase some things for his clients, but it’s not urgent. He needs to complete this task over the next two weeks.
Aaron’s process for commuting to IKEA would look like this:
At a specific moment during the week he needs to:
- Open Maps
- Search for an IKEA store
- Choose the route for which one is closest/shortest route currently
- Decide if now is the best time for him to do this task
The current solution is nice and easy. However it only referrers to a task being done right now. That’s not always the case.
Premise
As Google already knows the following:
- Where Aaron is at any given moment
- Where he needs to go (provided by him on maps/calendar/other)
- What’s the best Timing during the day/week/month to get there (Traffic wise, bus schedule, crowded places at certain times etc)
We can use all of this data combined, connect the dots, and get Aaron’s Best timing.
The Solution(s)
The Google Maps way
Let’s consider this non-urgent task as a regular Google Maps navigation.
While in search mode Google Maps may offer a Best Timing button that will let maps know that these situations should be treated differently.
A deadline and some properties might be useful here (preferences for specific days/hours that are more convenient etc.).
After that, Google’s magic does the rest. A Google Maps notification appears when the Best Timing arrives.
This will be calculated while combining the data with the user’s preferences (Google Coders: the technical solution is on you guys ☺)
The solution might look like this:
That’ll work, but it feels like this solution doesn't go “all the way”.
The Google Calendar way
While developing this idea, it occurred to me that these non-urgent tasks should be treated as… tasks.
A much more native approach leads the solution to reside in the Google Calendar space.
I think Google Goals is a great natural place for these tasks. However, some preferences are needed to filter and better adjust the Best Timing solution. By adding some settings we gain a one-stop-shop for these sorts of tasks. Google will keep them in mind, and notify you when your schedule, location, and traffic related data can result that golden path.
In addition to a Google Calendar notification, A snooze button can be useful, as “Now” is not always the best time.
Thanks for reading!
Would love to hear your thoughts, please comment here or by Gmail
Disclaimer and thoughts
Hopefully, you found this interesting. I wrote this article mainly to get these ideas out of my head, and make room for some more.
Regarding usage rights — of the above material and/or screenshots belongs to it rightful owners of course.