Kurviger 1.13.16 (Beta)

(we can also discuss that in the relevant topic)

I am available for changes if there is enough feedback - not many have participated so far.

Are there any DIS-advantages?
If not - me I always prefer more options compared to less.

1 Like

Ein Mehr an Auswahl kann aber Nutzer abschrecken, wenn es zu viel wird. Zumal ich nicht denke das sich Alle die FAQ oder das Handbuch durchlesen. Ich denke die Meisten werden sich, so wie ich, die App installieren und losfahren wollen. Ohne sich groß Gedanken machen zu müssen welche Einstellungen Jetzt die richtigen wären. Deswegen finde ich Weniger aber Bewährtes persönlich besser.
However, more choice can deter users when it becomes too much. Especially since I don’t think that everybody reads the FAQ or the manual. I think most of them will want to install the app and get started, just like me. Without having to think about which settings are the right ones now. That’s why I personally find less but proven things better.


This we had discussed often in this forum as well.
Problem is:
WHO’s the one to decide, which options are more useful and which are less useful?
Only in very few cases can an agreement be reached.
And then any restriction of options is a loss for at least one part of the target group.
Therefore, it is better to leave the options as they are, if they have already been implemented by the developers, i.e. do not require new efforts.

1 Like

Ich gebe Ihnen dahingehend Recht das die Funktionen momentan eingebaut sind. Was wir aber nicht vergessen dürfen, dies ist eine Beta-Version welche, meine Vermutung, nicht durch die breite Masse genutzt wird. Betas sind zum testen da, wenn festgestellt wird Ok das passt oder passt nicht, werden entsprechende Änderungen vorgenommen oder alles gelassen wie es ist. Im Forum habe ich auch schon von @devemux86 gelesen, das nicht alles unumstößlich ist. Vielleicht hilft manchmal eine Umfrage weiter wer welche Funktion nutzt? :thinking:
I agree that the functions are currently installed. But what we must not forget, this is a beta version which, my guess, is not used by the masses. Betas are there for testing, if it is found Ok that fits or does not fit, appropriate changes are made or everything is left as it is. In the forum I also read about @devemux86, that not everything is irrefutable. Maybe sometimes a poll helps who is using which function? :thinking:

1 Like

I agree … and I’d like to keep the “Settings | Routing | Waypoints in instructions” for same reasons.

1 Like

Yes, absolutely. Now it’s clear that rerouting only considers the next regular (“via”) waypoint without loosing all the shaping waypoints following after it. Sounds quite perfect for me (will be tested as soon as possible). Thank you. :+1:t4:

I would agree with that. I think “nearest route point” and “nearest waypoint” could be removed. I don’t think those options are very useful. But depending on the route and your current position they could have quite undesirable effects.

Hmmm, usually I also prefer to have different options to configure a tool for my personal preferences. But too many rerouting options may confuse unexperienced user (or those who didn’t follow all the discussions in this forum :wink:).

Yes, reasonable point.

Hmmm, yes - maybe you’re right. I’m really very torn … :thinking:

And what then about the minorities? This would only make sense, if any option has NO proponents at all.
Not to be expected. :smiley:

But perhaps better outsource this fundamental question, how to deal with multiple “necessary or unnecessary” options and the “overloading” with possible options, in another thread?

(That’s up to @devemux86.)

Polls hold only a small part in the non-deterministic development algorithm.
As a developer more important are stability, performance and maintenance.

By the way please let’s continue discussion for rerouting options in its topic:


Coming again in next (beta) version. :slightly_smiling_face:


Kurviger 1.13.6 (Beta) is on Google Play (instructions):

- Navigation: improve rerouting settings (Pro)

- Navigation: improve rerouting at start (Pro)

- Navigation: improve BRouter turn instructions (Pro)

- Map: option to group markers

By clustering the markers, we can put a large number of markers on the map without making the map hard to read and hurting app performance.

Available in “Settings | Map | Maximum zoom level of marker groups” for bookmarks, GPX, etc.

- Various improvements


sounds good, not yet available on my device, probably takes a while… but I have another question:
since 1.13.2 it should work to rename Waypoints and switch between regular and shaping. This is not working for me. Nothing happens when I long-press on a waypoint (still 1.13.5).

When long press on (yellow) via points or (white) shaping points, their dialog appears with different actions per type. The via points offer the “Edit” action to rename them.

Long press menu on waypoints works if enable the “Settings | Map | Crosshair placement”.

1 Like

Ah ok, yes, then it works. Thanks.

4 posts were split to a new topic: Drag waypoints?

Hi. Yesterday I tried Strict navigation mode on our 360 km trip. Everything works as expected :+1:
But, after one pause on route, I turn navi on again and it starts to beep after every instruction. I was on route and I have Off route warning disabled. I’ve never seen this behavior…

settings | Voice guidance | frequency of tone away from route?!

I have it Off

Do you mean that you stopped completely navigation and started it again?
Then obviously it understands that you are not following the route “strictly”,
but started navigation on a random point along the route, in flexible mode.

With strict navigation, cannot start navigation anywhere after 1st waypoint.
You can skip all waypoints before your location for strict navigation to work.

“Navigate along the route without shortcuts, i.e. follow the route strictly from one waypoint to another. When go off route, the rerouting tries to resume to the last omitted waypoint.”

Yes, we reached one of waypoints, where I stopped navigation and after break I started navigation again. I did this at every waypoint but beeps started only after last one.