Piwoslaw -
I think the "output" should be suppressed based on what the user is doing. When we talk to a passenger in the car, the passenger is also aware of the outside surroundings and will react to situations (be quiet or go "eeek"!). When the driver brakes hard, the passenger knows what's going on and will stop talking (good). This *doesn't* happen when someone is on the other end of the phone (bad). The interface can also have access to this information, so why not make it go "eeek!" or follow policy X that the user has defined?
Ha ha, they've got radar in cars, why not have all output suppressed when the car detects that the driver's velocity puts them within the "3 second" rule? :
The 3-Second Following Distance Rule | Driver's Ed Guru
Quote:
How the 3-second rule works
The 3-second rule is a simple way to double-check that you are driving at a safe following distance. Choose a fixed point that is even with the car in front of you. For example, a road sign or a building. If you reach that same fixed point before you can count to three, then you are driving too close to the car in front of you and you need to fall back a bit.
|
This would force drivers to "make space" around themselves in order to use the gizmos. It could also shut down when the national speed limit is exceeded.
CarloSW2