New beta! 6.0.0 (514)

[Stephen Rowland]

Wow, I’m starting a 2000mile trip around France on Saturday. I’m going to be testing this new version and I’m quite excited. Though I do hope there’s not too many issues.

[RetiredWingMan]

Riding season is almost over here in Canada! I won't have time to try out all the new features! I will try.

[a white mouse on the motorbike]

@Hubert-Thoring said:

Let's go just loaded for iOS

@hubert-thoring; Yes, go on then, rub it in for the Android users!

@hubert-thoring; Ja, wrijf het er maar lekker in voor de Android gebruikers!

[Stanisław]

I took a short trip home yesterday with the new beta and everything worked smoothly with no problems, good job! The new resizing is good for roundabouts, etc., but I'm not sure if it's enough for curvy roads – I have to do some more experiments. In my opinion, it could be more effective at lower speeds – the curves would be bigger.
The bottom part with the swipe-up gesture is great!
I have two ideas on how to improve the new beta:

1. Section-based speed measurement: the new bar is fine, but why doesn't it show the current average speed for the section? Would this be possible?
2. The trip line at the bottom is a good idea, but not very useful for long trips. It would be perfect to see only the next 50 km, for example(maybe as a configuration setting), with small fuel station icons on it . Could @corjan-meijerink think about it?

[Hubert Thoring]

For information:

Just noticed, in the announcement it says (514) in the app it is under iOS but now that I have looked it up (515).

[Rob Verhoeff]

@Hubert-Thoring nothing special in navigating! Just a minor issue that you won’t even think of! It’s not even worth mentioning

[ValléeDesFées]

when do you expect to have it available for Android?

[a white mouse on the motorbike]

If it takes as long as the last update, it will take about 14 days. So sometime towards the end of the first week of October.

[Guzzist]

Do I miss anything? My actual version is 5.2.2. - 489 - but you are talking about 6.0.0. - 514. Because there is a big gap in version numbers (digits). Or is it the usually delay of Android PlayStore?

[a white mouse on the motorbike]

@guzzist; I suppose you did not read the first post on page 1!

[ValléeDesFées]

@a-white-mouse-on-the-motorbike thanks!

[Hubert Thoring]

@Rob-Verhoeff sagte:

@Hubert-Thoring nothing special in navigating! Just a minor issue that you won’t even think of! It’s not even worth mentioning

What exactly is it, ...

[M. Schrijver]

Yesterday i was reading a navigation topic on another forum. This was about a different app. This app has also long approval times at Google for the last few versions in the past few months. So it doesn't seems MRA only

Yesterday i was reading a navigation topic on another forum. This was about a different app. This app has a long approval time at Google for the last few versions in the past few months. So it doesn't seems MRA only

[Corjan Meijerink]

@M.-Schrijver Google is terrible at the moment

[richtea999]

Two of my Android apps went through in 3 hours last night (not to rub salt in the wound!).

They're a lot less complex than MRA, but I suspect it's to do with permissions requested (such as location, storage, access to device sensors, etc) which are a higher risk to users from Google's point of view, and need to be thoroughly tested. Maybe there's a location-specific test team and they're overwhelmed?

Just politely let Google know they're falling behind the competition, and it's reputationally embarassing.