I would prefer a simpler route versus a faster route, with a lot of turns or merges.
I'd like a setting to take the simpler route, if it is only a few minutes longer.

Many times the added efforts of following the maze routes created/generated result in negligible time/distance savings. Why not reduce the driving effort, reduce driving distractions created by the route, and improve attention dedicated to driving safely, instead of turning frequently?

Waze often struggles to cope with the high-density population and the consequent difficulty of navigating through Manhattan, New York's tight turns. When Waze attempts to avoid particularly congested routes, it often leads to more frequent turns, resulting in longer travel times for drivers and potentially increased chances of encountering pedestrians and traffic violations due to more frequent turns. Therefore, I suggest that Waze introduce an option that allows routes with fewer turns, even if it means navigating through worse traffic conditions, to minimize unnecessary turns. Implementing such a strategy would align with the expectations of many drivers.

In my view we need the following routing options: a. Left (or right) turns only - to minimise crossing "oncoming" traffic. b. As the crow flies (straightest). c. Minimum turns (even if it is longer). d. Minimum roadworks. e. Minimum traffic. f. Minimum speedbumps (they are seldom correctly marked and damage your car's suspension). g. No dirt roads. h. No toll roads. Currently you only offer dirt/toll avoidance as options, and currently it seems to favour "as the crow flies" which ends up making you perform zigzags through cities. We need more relevant options. I find that just tolerating a traffic jam reduces the number of turns I have to make and generally only wastes 1-2 minutes. I am prepared to take 1-2 minutes longer if I do not have to turn.

Quite often, what I do to avoid your routing algorithm's excessive turns, is I will identify a target turning point on the map and use it as a stopover point on the route, to force waze to minimise turns. I can send you screen shots to show you what I mean.

Navigation within built-up area (in cities or villages) works wrongly. Instead of one simple and safe turning, it navigates into a lot of zigzag operations on minor roads which result unnecessary turnings and dangerous situations (more crossings, etc.). Sometimes the proposed way can not be safely used by cars (narrow, quality is bad for permanent traffic, etc.). Other applications do not do this. Otherwise, out of built-up areas, works well. Navigation mode should be able to set by the user, or make some fine tuning on that. At the moment, it seems that the shortest way is used. Please add more navigation mode, for example shortest, fastest, safe, minimal operation, etc.

When The navigation sends me a way and a turn is not allowed it doesn’t reroute even though I say the turn is not allowed. When I click turn not allowed and click reroute, give other options for navigation.

In the merit of avoiding congestion, waze sometimes send drivers into swirling of twists and turns. All to cut just a minute or two. I suggest adding a 'best comfort' route which will prefer routes that are up to 5% slower, but have 50% less turns than the fastest route.

This is so needed on the shortest distance routing option. I have turned 5-6 consecutive corners to save 10 feet. Some penalty for stopping to turn should be added to shortest route to save time, gas, wear and tear, frustration, etc.

The route type gives the option of fastest or shortest. I would like to see the option of fastest and shortest. Sometimes fastest has you turning every block versus a straight route.

I've been wanting this since I started using GPS apps on my phone. I want less complicated directions. I'm willing to drive an extra 5-10 minutes if it means I don't have to worry about as many turns.

In an area I've been recently "shortest" and "fastest" routing options will wind me through crowded neighborhoods; rather then main roads and fewer turns.

Example: If you can get from point A to point B with a single left turn, this simple route should be preferred over a route that gets there with six alternating left and right turns (even if the simple route is slightly shorter in distance)

Example: If you can get from point A to point B with a single turn, the simpler route should be recommended over a slightly shorter route that gets there with several alternating left and right turns.

Now we have 2 route options: shortest and fastest.

There are no doubts how shortest is calculated.

Fastest route is somehow tricky as I have noticed. It is truly fastest intracity routing. A quite regulary drive routes more than 100km. This makes difference. Routing server tries to avoid driving through cities. This is completly wrong and I most of the time ignore directions to take highway. Driving through cities is faster always even in congestion time. I know it is a lot harder but it's worth that. Some have noticed that this routing preference change ocurs roughly on 10km route. I can presume that this is done to preserve routing server resources as there are a lot more road segments per distance in cities than countryside.

I read soon Waze infrastrucure will be capable of dealing with additional work. My suggestion is to rename route "fastest" to "easy" and make new one "fastest" routing option that routes through cities even for longer drives.

What do you think about this?