This is the feedback thread for the Kurviger App update 3.0.9. We are looking forward to your feedback.
If you would like to request a feature or report an issue, I would like to ask you kindly to create a separate thread for this as it can get a bit hard to follow the discussion in one huge thread. This thread is about discussing the features that we have implemented with 3.0.9 update.
Ich muss grundsätzlich für mich und meine Anforderung sagen, dass ich diese Neuberechnung nicht brauche, da ich die App nur zum Abfahren von Routen nutze. Deswegen ist die Neuberechnung auch abgeschaltet und ich würde mir dann auch wünschen, dass dieses dominante Feld mit Manueller Neuberechnung auch nicht erscheint.
Danke für das Feedback. durch das Feld fehlt dir ja nicht wirklich Karten-Platz, da sonst an der Stelle die Zeit und Distanzanzeige ist. Wir können mal schauen ob wir das noch weiter optimieren können.
So heute mal 80km gefahren.Kein nachhinken des Pfeils sehr exakt.Mit 44% losgefahren und mit 39% angekommen waren ca.2 Stunden.Bin begeistert.Sehr nahe an K2.
Jetzt noch die Individuellen einstelleungen,wie Schrift,Farbe der Route usw.
Today I drove a route of 140 km. Works fine for me. Battery was charged to 100% (Samsung S9+) with remote charging. The fact that the arrow appears when you are off the route works great. It would be better if you zoomed out further, so that you have a better overview of where the route is located. As soon as you are back on the route, the normal zoom function returns.
Possibly an option to disable the zoom function at turns. Because when you zoom in, you sometimes don’t see that there is a better route. This is sometimes in cities or when a route first goes off the road to rejoin the road a few hundred meters further on.
I have a minor update request, which might sounds odd: The old version always said, when the route is calculated new. Since I am only use routing-by-ear it was always useful if I e.g. took a wrong exit at a roundabout. Probably a lot of users don’t like that and are happy that the app now calculate silently, but for me it was quite helpful. Would it be possible to add a sub-setting to add this option?
Just to conclude our discussion from the previous version…
For one of those roundabouts I have corrected the data in OSM - disabled the improperly allowed turning left at the exit and added the tag for being the roundabout (to be recognizable as such) - some 4 days ago, usually it takes couple of days, until the modifications are visible in Kurviger.
You may modify the data in OSM for other roundabouts or streets in your neighborhood, if you find them being inappropriate, to get better routing and navigating experience…
…you may do the editing with the little help from LearnOSM, as I do…
The GPS arrow is no longer so far behind. However, it seemed to me that sometimes there was still too much delay.
It would be good to fix the portrait/landscape format, because depending on the position of the curves, it tends to rotate and then stays that way until the next “correct” curve.
I have deactivated the automatic rerouting. I liked the box for ‘Recalculate route’ when you are off the route. It’s clear and can’t be miss when you need it.
I left the route twice (on purpose) to stop at nice viewpoints. The first time everything worked again when I was back on the route. The second time, unfortunately, it didn’t. I was back on the planned route but the app didn’t recognise it. For test purposes, I then drove to the next shapping point because I thought the app would then notice that I was on the route again. But that was not the case. I then pulled over, stopped the navigation and restarted it, then everything was fine again.
Overall, the app already runs very well for my requirements. The requests here in the forum are also largely the same issues. I am convinced that work is already being done on the open requests and that we will soon have a stable running Kurviger app.
P.S. May I already cautiously ask about the pricing model for the new app?