⚠ Have you searched for similar, already existing issues?

Yes, I did.

Is your feature request related to a problem? Please describe.
One of the major consumers of phone battery is the screen. When hiking, it's quite common to arrive to a path juncture and have to fish the phone to see which path to take.

Describe the ideal solution
One way could be to consider the juncture like a roundabout, count the paths counterclockwise, and make the phone vibrate and or emit a sound the amount of times as the number of the 'exit' to take. TBH, this could work for car or bike navigation too.

Example:

https://www.openstreetmap.org/#map=19/43.23111/5.46307&layers=P

You're approaching the Col Ricard from the North/East and the navigation says to go to the South West exiting via the T1. First you get one notification to take the T1 path at thew Col, then two notifications when you cross the T2 to keep going straight (or maybe none, since you don't have to actually turn).

Of course, this all depends on whether the current data structures allow to make these calculations.