Certain apps have the ability to detect what Bluetooth device is connected.

My suggestion is to allow users to pre-configure different Bluetooth connections to different vehicular modes, for example, a Bluetooth headset may be used on a motorbike and therefore Waze could detect that this Bluetooth connection is present and set itself for motorbike mode, likewise, an in-car radios own Bluetooth connection could be configured for a car, and finally, a different Bluetooth connection could also be configured for a truck, I envisaged then that this would allow users to predefine certain options like toll passes, low emission zones and parking restrictions etc. All based on the current Bluetooth connection method.

For example, motorbikes are allowed toll-free within low emission zones and also are free within toll roads, this could be allowed to dynamically configure routing for the motorbike where it will be optimal to use tolls as they are free, whereas for cars, there may be a toll pass required, or for trucks certain roads are impassable, again, this all could be dynamically pre-configured by the user depending on what device it is connected to on Bluetooth.

Currently, the user interface for changing between cars and motorbikes and adjusting any toll or highway settings is very cumbersome and requires a lot of user input to change between the two. Also, this may lead to unexpected charges if a motorbike user forgets to change Waze from motorbike mode (where tolls are free) and inadvertently uses Waze while still configured for motorbike mode while driving a car.

The clunky user interface does not invite users to easily change between the two.

Furthermore, the ability to easily change between different vehicular modes allows users to pre-configure. For example, a motorbike may not wish to go on a motorway where as the same owner may wish to drive their car on a motorway. Having the ability to pre-configure motorbike to car to truck depending on Bluetooth connection method I feel is a useful system update