Re:UX Issues That Will Make Or Break Self-Driving Cars
by dogma1138 on Saturday March 19, 2016 @08:33PM
(#11321203)
Yes and no, that may hold true for specific mission autonomous applications e.g. metro transportation, sanitation, cargo transportation etc.
In these cases the the vehicle and to some extent the environment is much more controlled and it configured for optimal operation.
On the consumer side it's a completely different story because not only does the autonomous driver needs to outperform the human driver it needs to do so in a case when you have compound errors if the driver of the car does not trust what the auto pilot is doing you'll get into more accidents not less, and in a market environment where you have a very broad range of features you can inconsistencies which lead to more accidents.
And this is where you hit the UX issue, all autonomous drivers have to present a reliable and consistent user experience to avoid compound errors that arise for the involvement of the human (jeez that sounds eerie too natural these days) driver.
When I step into a car with an auto pilot I need to know that it will get me from A to B with minimal supervision and will on it self avoid obstacles no matter what car I step into.
If car maker A is allowed to sell it's auto pilot without collision avoidance for example while car maker B has it it will create confusion which leads to accidents, if car maker C then decides to sell an auto pilot feature which is nothing more than a glorified cruise control it can lead to even more accidents.
This is why some standardization is really needed with this tech getting off the ground.
The standardization also has to go beyond sheer features it has to provide a consistent user experience across the board so things like acceleration, breaking distance, driver alerts etc. need to be more or less consistent across different cars from different manufacturers or again you'll can get an increase in accidents due to driver errors.
In these cases the the vehicle and to some extent the environment is much more controlled and it configured for optimal operation.
On the consumer side it's a completely different story because not only does the autonomous driver needs to outperform the human driver it needs to do so in a case when you have compound errors if the driver of the car does not trust what the auto pilot is doing you'll get into more accidents not less, and in a market environment where you have a very broad range of features you can inconsistencies which lead to more accidents.
And this is where you hit the UX issue, all autonomous drivers have to present a reliable and consistent user experience to avoid compound errors that arise for the involvement of the human (jeez that sounds eerie too natural these days) driver.
When I step into a car with an auto pilot I need to know that it will get me from A to B with minimal supervision and will on it self avoid obstacles no matter what car I step into.
If car maker A is allowed to sell it's auto pilot without collision avoidance for example while car maker B has it it will create confusion which leads to accidents, if car maker C then decides to sell an auto pilot feature which is nothing more than a glorified cruise control it can lead to even more accidents. This is why some standardization is really needed with this tech getting off the ground.
The standardization also has to go beyond sheer features it has to provide a consistent user experience across the board so things like acceleration, breaking distance, driver alerts etc. need to be more or less consistent across different cars from different manufacturers or again you'll can get an increase in accidents due to driver errors.