The navigation apps street number problem

When I design navigation apps and sites I always think how to keep users researches fast, efficient and correct. In my experience, even as common user, the address research is a real complex phase for two main reasons:

1) Typing mistakes caused by complex street names, sometimes even in languages that users don’t know. In Italy for example, a part from the Italian language, we call streets and squares in different ways depending on their dimensions (street= via, viale, vicolo, corso etc; square= piazza, piazzale, largo etc)
2) Inserting the street number using the autocomplete/suggestions drop-down list

While regarding the point 1 I could imagine that a motivated user could type or paste the correct address, the point 2 drives me really crazy.

Watch below what happens on Uber and Here when I use the suggestions typing my wife’s massotherapy studio address in “via Durini, 15”.

When I tap on the suggested address the research phase ends brutally locating the pin point in a default position of the map that usually is the street number 1.
But what if I’m searching number 299?
I must go back modifying the text and risking to invalidate the address, or I must type again everything, street number included, ignoring the suggestions.

That’s the navigation apps street number problem.

In the last weeks I discovedered that Google Map solved the street number problem in a brilliant and simple way. They indeed created a dedicated button for the street number directly on the suggestions/autocomplete drop-down list. Watch the video below.

This solution is available both when the user must chose between a lot of similar addresses or when he/she already typed enough letters for having the correct address. Following the two examples.

Thank to the Google Map new street number button, now I can search “via Durini 15” following theese simple steps:

type “dur” > tap on “street number button” > type “15” > tap “enter” > see my perfect location on the map!

For improving this process I could only suggest to switch to the number keyboard when typing the street number. I know that sometimes, like at our home, street numbers are like 1/a, 1/b etc, but usually these subordinates are not as far to compensate the experience of seeing just numbers when you asked to type the street number.

I hope to use this kind of solution in my future projects, but I’m pretty sure that soon it will be adopted as an industry standard from all the navigation apps decresing the adoption cost.

In the meanwhile, thank you Google!

Leave a Reply