Feature Requests: Fastest Route Without Highways & Easier Waypoint Skipping

Route planning
1

Hi,

First of all, thank you for the great work on Kurviger. I use it mainly for motorcycle touring and I really appreciate the route planning flexibility. However, after using it extensively, I feel there are two areas that could be significantly improved.

1. Missing routing mode: “Fastest route without highways”

Currently, for each segment between two waypoints, I can choose:

  • Fastest Route

  • Fast and Curvy

  • Curvy Route

  • Extra Curvy Route

There is also a global option to avoid highways/toll roads, but that applies to the entire route.

What is missing is a very common real-world use case:

I want to reach the interesting riding area quickly, then enjoy scenic roads, and finally return home quickly again.

For example:

  • Home → highway allowed (reach the mountains quickly)

  • Mountain area → no highways, no toll roads

  • Return home → highway allowed again

The problem is that if I want to avoid highways on a specific segment, my only alternative is to choose Curvy or Extra Curvy. But these options are designed to maximize curves and detours, which is not always what I want.

Sometimes I simply want:

“Fastest route while avoiding highways and toll roads.”

No special search for curves, no additional detours, no motorcycle-specific optimization. Just the most efficient route using normal roads.

A practical example is crossing Switzerland to reach Airolo. I may want to avoid the motorway, but that does not mean I want Kurviger to send me on hundreds of extra curves and detours. I simply want the quickest non-motorway route.

I believe a routing mode such as:

Fastest Route (No Highways)

would solve this very common scenario.

2. Android Auto: skipping a waypoint requires too many actions

On Android Auto, the bottom-left box showing the next waypoint is very useful.

However, when selecting that box, the primary action offered is to stop navigation.

In practice, when riding a motorcycle, the most common need is not stopping navigation but skipping the next waypoint.

Today, skipping a waypoint requires navigating through multiple menus and several clicks. This is particularly inconvenient and distracting while riding, especially because many motorcycle handlebar controls are not very responsive when interacting with Android Auto.

My suggestion:

  • When selecting the “Next Waypoint” box, provide a direct Skip Waypoint action.

  • Alternatively, show both options immediately:

    • Skip Waypoint

    • Stop Navigation

This would reduce rider distraction significantly and make waypoint management much safer while on the move.

I believe both improvements would make Kurviger even more practical for long-distance motorcycle touring.

Thank you for considering these suggestions.

2

Hello @Marcick,

Thank you for your feedback!

  1. I understand your wish. We deliberately chose not to allow avoidances per segment as it would increase the complexity of the interaction of curvature and avoidance settings, when we actually want to keep it predictable and easy to use.
    That said, we plan on revising these settings anyways and I could imagine that the current “Fast and Curvy” option might fit as a “Fastest without highways” type of mode but that is yet to decide.

    As a workaround, you could split the route into two routes (one for the ride to the actual riding area and one for the twisty ride itself), or add a few more waypoints to the segments where you want to get a fast route while avoiding highways.

  2. On Android Auto we don’t have as much flexibility as we have in the Kurviger App. The button you’re seeing, which currently ends the route, is more of a side effect of how we implemented that feature and I am not sure if we could add a “skip next waypoint” function instead.
    However, the box doesn’t just show the next waypoint it can also show the final destination, depending on your settings. In the latter case, a button to skip the next waypoint might no longer be as intuitive there. We’ll review if the skip next waypoint function needs fewer clicks (currently it’s three).

We appreciate your feedback and keep it in mind as we continue to improve.

3

Hello,

Thank you for the reply.

I’m a software developer myself, so I know how valuable user feedback can be.

The workaround you suggested is actually what I’m currently doing. It works, but it’s a pity having to split a full-day motorcycle trip into multiple routes, because you lose the immediate overview of the total distance and riding time.

I understand your concern about keeping the interface simple. My feeling is simply that “Fastest without highways” is such a common use case that it would fit naturally as a routing mode.

Thanks again for taking the time to consider the suggestion

4

It would be better if you post this feedback in a separate topic, since it has nothing to do with routing options. Currently there are also similar posts in different topics, which are then difficult to keep track of.

Maybe this topic could be “recycled” - Icon "Überspringen" in Android-Auto fehlt if @moderators would change a title to “SKIP function on Android Auto” (or similar).

5

Hello dear Kurviger Team,

please excuse for dropping in.

You stated the following in the above post:

That feature (choosing avoidances per segment) is exaclty what I am currently missing in Kurviger.

I think it can be implemented without making route planning to complex, because I don’t HAVE TO choose different avoidances per segment ( I can just leave the avoidances the same for the whole route), but I want BE ABLE to choose different avoidances per segment.

Using the route characteristics settings (fast - very curvy) to control the usage/avoidance of highways ist kind of breaking the logic of the two (separate) route parameters (rout characterstics versus street avoidance). At least in my eyes. Why should we have avoidances at all if we can control usage of routes via charactderistics?

And: If I choose Highway avoidance (tier 5) for the whole route, and I choose fastest route for the first section of a route, why then will it use highways? For me this is unlogical and it is contradicting my avoidance settings.

So I want to ask for that feature: (optionally) using different avoidance settings for segments. Maybe it helps if this feature can be enabled/disabled in the settings menu, so that users who do not want to use it, can switch it off?

6

Hy ,

if you know the way doing this around AA definition´s y are welcome :upside_down_face:

7

You’ve really hit the nail on the head here: The interplay between “curvature” and “avoidances” is hard to grasp in some places, and as I’ve already written:

8

Hello Kira,

thank you for commenting on my post and reminding me that you plan to revise this.

I am quite interested in the next iteration.:smiley:

9

I appreciate the complexities of the implementation but I just took a 3000 mile trip trying to use Kurviger and REPEATEDLY had issues where I would go to a waypoint and for whatever reason it didnt register, and it would subsequently keep trying to route me back to where I had already been. In multiple cases, this caused me to take turns I wasn’t supposed to take. Being able to more easily skip the next waypoint is by far the most important feature I am missing and the only reason I had to intermittently stop using Kurviger and switch to a different mapping app during my trip.

10

Could you maybe share an example route where this happened? Usually, when your via points are on your route, they should be registered as visited. Maybe they’ve been set too far from the route?

In your case, skipping waypoints feels more like a workaround for an issue that shouldn’t normally occur. In a standard navigation use case, we assume waypoints are skipped only occasionally (let’s say few times per ride). That’s why the current interaction takes three clicks. So I would rather try to find out why the navigation behaved odd in your case.

11

When using the handlebar controls to operate CarPlay/Android Auto, the system often feels slow to respond. Having to make those three clicks forces you to take your eyes off the road for too long while watching the screen to see where the cursor is.

In my opinion, skipping a waypoint should be much easier. I use the Skip Waypoint function frequently, and quite often I end up stopping the motorcycle just to interact with it safely.

12

That’s the right way to go about it. However, instead of waypoints, you can also use shaping points. That’s how I work, just so I don’t have to skip anything.

13

I use shaping points extensively, but they serve a very specific purpose in route calculation only.

What I’d like is to see the next waypoint, along with its TOA, on the screen and have an easy way to skip it if needed. Converting waypoints into shaping points isn’t the same thing.

That said, we’re really talking about minor details here. It’s not a big deal—we’re just offering suggestions for possible improvements.

14

I do understand your feedback regarding a shorter way to “skip waypoint”. However: If your navigation repeatedly forces you to skip waypoints you already visited, it might be more helpful to try and resolve the underlying issue. It sounds a bit odd and the behavior is hard to understand without seeing the route.

One tip for you that might already help a little: Use via points only for stops or locations you definitely want to visit (Kurviger will “force” the route via those). And use the feature “snap waypoints to road” in the three-dot-menu in planning view so our waypoints will be on the road and not accidentally next to it.

It is not normal that you have to skip many of your waypoints in order to continue navigation.

15

Thanks for your reply. I think it is both issues. One is that sometimes a stop doesn’t register. Other times I might decide to skip a stop and the navigation can’t seem to ‘move on’ without manual intervention. I agree that for stops I think I might skip, a shaping point would be preferred.

In one case at the Lake Louise Summer Gondola, I struggled to remove a stop I had already visited due to spotty cell connection and the navigation appeared to be updated, but upon restarting my bike at the next gas stop, the previously skipped stop reappeared. I may have made my route too complex by trying to run the whole long trip from one map. The link is https://kurv.gr/UXHCE

16

Placing your Via-Points at the Route or at the actual place where you are able to stop/park with your vehicle might improve the situation. Some POIs like larger shopping malls or viewpoints may be too far away from drivable roads.
Kurviger can support you with the function “Snap waypoints to road”, but beware that you may need to reenter the waypoint names if they were automatically varried-over from a POI.

Screenshot_20260716_080247
Screenshot_20260716_0802471080×1394 79 KB

Screenshot_20260716_075628
Screenshot_20260716_0756281080×993 170 KB

4900km is a long route. Although the App can still handle it, there are some disadvantages:

  1. At that lenght you are getting close to the limit where the app cannot calculate the route due to technical limitations - sometimes it hits already around 6000km, sometimes 8000km - it is not directly dependent on the kilometers, but on the system you use. There are several discussions about related issues on the forum, like these: Too long route bug - #24 by boldtrn
  2. The route takes longer to recalculate if you make a deviation or skip a waypoint.
17

I also checked.

Some waypoints are quite far from the route, using the funtion to place waypoints on the route may help, as @t00thl355 said.

A lot of points are via-points; most of them should be shaping points, but I can only guess, as I do not know, if you really wanted to visit these points. Very comfortable in the app, click the waypoint, in the popup click the waypoint, then it is toggled to VP/SP and vice versa.

Advantage of SP is that these are automatically skipped.

Automatic skipping when waypoint us reached ..
A SP is normally skipped when it is “behind” you or you reached the point. A VP is skipped when you reached the point.

To my experience is “reached” at about 300 - 500 m (330++ yards). In other words - gps signal is also important. I prefer on Android phone the Location Service -Android.

To my experience less power consumption and more reliable gps. Why is some exact WLAN based location necessary, when I am far away from some village/city?

Bad internet. As far as I know, skipping requires not just internet connection, but also a good gps signal. Perhaps some skipping was in a building with limited internet and / or gps?

For point 45 is a warning, my guess here is that this is not your intention. Click the “Info-Button” in the app to see warnings and double check. Very helpul feature. In this case you are routed back from 45 to 47. Can be unexpected.

Screenshot_20260716_154820
Screenshot_20260716_154820720×1523 278 KB

The route is very long. My estimation is that it took more than 10 days?

@t00thl355 already listed some disadvantages. I would add here some more. To be honest, more theoretical, I can not prove anything.

The app can have for this long route at any time a “hickup”. Also it could happen, that you get some updates for Kurviger, system apps in these days, which can make a “hickup” more probably.

Snap to route: Perhaps some setting to always snap to route? For me it is always the same routine. Plan, snap to waypoints, always. I would set it to Always snap to route.

Long route. It works, yes, but I would split.

My question would be @Ryan_G why you did not split? Function is hidden, to many clicks to access it, not easy to understand, organizing the original route and splitted routes in a dedicated folder, splitting in 10 days time consuming, ..

I often think it would be helpful to be able to create a new route folder, when I save the route the first time. Today I must cancel the process, create folder, then second try to save. Then I could use this folder to put the splitted parts as well. Process would be straight forward.

Also (and already discussed), the split functionality is a really great functionality and should be moved to main menu. The users would play with it and learn, get some muscle memory.

18

I ended up doing it in 8 admittedly long days. I will try both shaping points and splitting the trip for my next longer trip. Overall I have really liked Kurviger and appreciate the great features. Thank you also for the feedback to my inquiry.