A side question to this one. Is there any guide-set or set of rules to judge which information is more important than other when designing a map-like mobile application?

When using Google Maps in driving guidance mode, I:

  • see a totally useless (from my perspective) information -- street name -- nearly all the time,
  • don't see an absolutely crucial information -- ETA -- until the very end.

Here are some examples.

  1. 190 meters till possible turn and no ETA:

enter image description here

  1. Less than 150 meters and still nothing:

enter image description here

  1. Only forty meters for a decision and still no ETA:

enter image description here enter image description here

  1. Last "capture", ETA appears when you're already in the process of turning:

enter image description here

Either I am missing something totally obvious (and would really appreciate an explanation here) or the whole ETA functionality has a purely wrong design. From the decision-making perspective I don't need street name at all, but I do need ETA on all the alternatives.

In mobile Google Maps this is made exactly opposite -- unimportant, useless information (street name) very often covers most important one (ETA).

Is there any specific reasoning, guide or rule set:

  • in general -- to decide which information is more/less important and thus must be shown above/beyond some other information in mobile apps design,
  • in this particular example -- that justify current mobile Google Maps design.
  • Just so you know, Google maps is showing you the ETA. In this image, red = ETA, blue = distance remaining, green = time remaining. – Manly Aug 9 at 12:50
  • @Manly This is ETA of CURRENT road. The question asks about ETAs for all the alternative ways, Google Maps suggests. But, since the question is found off-topic then there's no point in taking this discussion any further. – trejder Aug 17 at 7:25