I'm in the market for a car, and I want something new or new-ish, but I can't find any cars I like without touchscreens all over the place. I'm now looking at used cars from around 2012, before all the touchscreen nonsense became pervasive, but still with most of the modern conveniences I'm in the market for. I'm not in a rush so I might just wait and see still, but I said that a couple of years ago as well and the touchscreen craze has just gotten worse I feel like.
That said, car drivers really should get in the habit of making playlists so they can set up music and maps before they start rolling.
As a rider, I love the lack of distraction and can focus on everything going on around me, an important skill for staying alive on a bike.
I'm sure it can be distracting, but it is also easy to set up with minimal interaction.
Ultimately, it comes down to individual behavior.
The problem with all this is that it just depends. If I check a message after stopping at a red light? No real risk. If i hit "call" whilst on an empty straight motor way for a hands free chat? No real risk.
If I try and compose an email on a country lane, or find a specific artist to play, or set a reminder whilst driving through a town centre... quite a lot of risk.
My car still has cassettes, so I have probably taken more risk changing over those (where is that bloody mixtape I want) than the limited phone use I have done
If this were true cars wouldn’t have touchscreens built in.
Their approach is far better than the all glass, cost saving Tesla one.
It seems like a feature that no one would really care about either way that car manufacturers just seem to think people want. It may even be because its cheaper than to R&D a user friendly tactile system with enough features vs just throwing software at it.
Right now, CarPlay interfaces with steering wheel remotes in the standard way where prev/next buttons change tracks and volume +/- changes the volume. What Apple could do is this: add a toggle somewhere in the OS that remaps these to cursor controls. This would, without any effort required on the part of auto manufacturers, bring something comparable to the Mercedes control system to the majority of CarPlay compatible vehicles on the road, all via an OS update.
I have yet to find a car with a better UX (aside from road handling, which I find equally good, but that’s another topic).
Touchscreens should only be allowed in cars with self-driving capabilities, and probably only on the higher levels.
In some lists the scrolling wraps around. In some it doesn't. Sometimes it's a click on an item. Sometimes it's a shift to the side.
And the systems I've seen (in BMW's DriveNow) have the worst feature of them all. The main screen where you have your selection of things to do (Nav, Car options, Media, Radio etc.) is not a fixed list, it's an MRU list.
So, if let's say radio is the very last item on the right side of the main screen, and you chose it, the next time you go back to the main screen, it will be the first on the left side of the screen. Now use Nav, go back. Now Nav is the first item and radio is the second item.
It is my long standing theory that people who design car interfaces have never seen a car in their entire life much less have driven one.
(And just hovering/slightly touching the key will show the current setting in the display.)
I put a Sony XAV-1000 in my '07 Honda Fit recently, it was the only Carplay unit I could find with a physical volume knob. You can hold the volume knob down to activate Siri, so I never have to actually use the touchscreen. It's been very nice for Apple Maps/Spotify, I'd recommend looking into it.
(Personally, I don't think I find CarPlay any more distracting than any other in-dash screen; I'm not looking down at the car's built-in navigation system any more than I'm looking at Apple Maps on the same screen. But, I also tend to listen to podcasts while driving, so once they're playing and the map destination is set I rarely have much impulse to fiddle with things.)
That seems bizarrely counter-intuitive as a more-or-less standardized low-distraction interface already exists for car radios.
Okay, sure, you add the touch screen so you can do GPS and stuff, but is it really that hard to wire up a pre-existing car radio knob and buttons to an Android device along with some software to map twisting the knob to adjusting the audio volume and so on?
It just baffles me how little apparent attention was given to this sort of thing. I wonder if these people are dogfooding.
In what way is it cheaper to install seatbelts than not?
The Mazda does have the little wheel (it's down near the gearshift) and in addition the touchscreen on the display screen is disabled when you are in motion (which I think is a great idea). I adapted to it within an hour (I was coming from our older 2007 Honda Civic which has none of these)
The Honda does not have the wheel and you can use the touchscreen any time (which I think is a bad idea)
So a good compromise for you might be a Mazda (I think all cars will come with screens especially now backup cameras are federally mandated)
Well, the knob is fine - the CarPlay apps aren't. You can find the physical control by touch, but for any non-trivial operation you still have to actively watch the display as you fiddle the dial to get to the action (on-screen control) you need.
Which is dangerously distractive on the road and kind of irritating when parked.
Anecdotally, over the years I've been driving, a majority of potentially collision-causing mistakes I've made (and that I've noticed) have been when I've been cognitively distracted by navigation systems and was looking for a turn/exit or thinking ahead for a turn/exit.
I've adjusted to always prioritize real-time safety even if it comes at the cost of missing my turn and having to double back to get where I'm going. I believe that following nav directions in real-time comes at a safety cost, and am skeptical that many people both realize this and make the appropriate adjustments.
this probably varies depending on your spatial reasoning skills. my brother can take a quick look at a map and remember the connectivity of all the major roads and then navigate from memory. whenever I try this, I end up in a stressful loop of miss turn -> find place to pull over to look at map -> miss turn again. stress has a comparable impact to driving safety as distraction in my experience.
To me, this is where GPS shines. If I miss an exit, it isn't a big a deal because the GPS will tell me the best route based on my current circumstances.
Now, I don't care so much. GPS can route me back pretty easily if I miss anyway.
Some people are however, still unwilling to be delayed no matter the danger.
It does still happen sometimes, though.
Now I have a quite large navigation screen in the mid console and those optional arrows next to my speedometer. It really took some time to get me to not look and the centre screen. It took even longer to get used to just listen to what the computer lady says.
I can't understand how this centre screen has become a safe standard. Especially in countries like Germany where there is no speed limit. It's a toy for passengers.
I dont know how people can text and drive. I usually see cars swerving and driving way too slow into a high way and it always turns out they are texting up a storm when you look.
Give me a D pad, an OK and a Cancel button. And make a phone API that works exclusively by that and the sounds and chimes it outputs.
I just want every supported app to be in a top level list that I arrow through and OK. Then within any app the options are all navigable in simple ways. Overall functionality is reduced.
Voice control is a secondary system altogether.
Honestly, on 101 and 280 I see drivers texting all the time and they're driving right in the lane, no problems at all except being slow to react to what happens in front of them (which makes it obvious they're on the phone). I don't know how they do it. Even glancing down at my phone instead of the center console loses so much state.
Pulling over to make changes may not be the most convenient, but I think for me at least, it's safest.
There's no question that physical controls for the most common tasks in a vehicle (there are actually very few) take less attention.
Additionally, it seems like one great promise of software in a vehicle would be to augment and improve upon that fact by design. But it's terribly obvious that this has not been a design goal ever. The goal has been to take the familiar UX of your phone and transfer it to your car so that the media component is immediately familiar (this is nice), but all the while we could have been making the act of driving safer too...
In my car, if I want to increase the fan speed, I need to tap a small target, wait while the system lags out, and then tap a new target on a popup. Meanwhile, I’m trying to focus on the road at (effectively) infinity. It’s distracting and unsafe.
In my old, very well designed 1991 car, I could push the button to do this. It had two major benefits: it never moved and I could feel it. Touchscreens can’t replicate the feel of a button, but they could at least have the decency to keep controls in the same place.
I can literally tell it "Turn on driver seat heaters to 3 bacons" and it will set the seat heater to the max setting (1-3).
https://youtu.be/mV8h2doorrc?t=58
https://www.tesmanian.com/blogs/tesmanian-blog/voice-command...
So no, I disagree that physical buttons are safer than an NLP enabled infotainment/dashboard display where I can turn on/off and adjust things using voice. Without taking my eyes off the road and hands off the wheel.
This may well be better than using the touchscreen, but it's still bad.
But at least in my car I only need to select fan speed in the first menu then scroll do actually change it. This in a model x. But I was really responding to the "100% touch screen" statement.
In contrast, IIRC a 2007 Prius could do this type of voice command with no obvious difficulty.
The only bug I've found so far was when I said "open driver door" and it displayed "opening trunk" and it slammed it into my garage door!
...if you are from English-speaking country or you know English.
Does Tesla understand every language in the world?
Or: how would my father change settings in Tesla? Would he need to learn one English phrase ("Tesla/Alexa/Siri/Whatever, open Google translate"), then speak in his native language, then somehow speak the translated text to Tesla's system?
Currently in his car, he does that by pressing a button. Done.
I like CarPlay, and found in the Mercedes models that had the little control wheel in the center console it worked well, because you had a physical switch to interface with CarPlay, but had the flexibility of the screen. I'm no expert, but I drive a lot of different cars and that so far is my favorite way of interacting with CarPlay.
I'd still prefer a simple dashboard with physical controls though.
I think with the latest update I can also control the active suspension via voice which is the only thing I still use the display for while driving except for hitting cancel on the navigation once in a blue moon. Cancelling navigation might also be available via voice command now, I haven't checked.
In any case, voice and physical buttons (on the steering wheel) is much safer than touching or buttons below the screen the screen regardless. At least I feel much more in control personally when I can keep my eyes on the road and not glance away / feel my way to a spot on the screen.
I think you answered your own question.
Because of the problems I have with Siri, I end up using the touchscreen much more than I'd prefer. My latest defensive habit is to queue up enough audio for the trip and not touch it again until I arrive.
I would definitely prefer hardware buttons.
You can, if the car is made that way of course, but the software supports it. I would not buy a car knowing it's only a touchscreen. At least in my car, the radial controls the focus on Android Auto and press it down to select. The screen is not a touch screen.
The problem isn't OS itself, but applications. Android application developers are frequently implementing custom graphical components, that do not handle "presses" and "clicks" and instead try to directly interact with touchscreen.
Google have made a number of increasingly aggressive attempts to work around the issue — for example recent versions of Android try to infer purpose and interactivity of custom UI elements instead of expecting developer to declare it. But that does not help, when everyone is using a handful of fancy libraries, hardwired to require touchscreen.
Incidentally, the biggest offender is not a third-party component... It is RecyclerView — Google's official item list implementation, distributed as a separate library. It's support for DPAD navigation is so abysmal, that Google's own engineers (from different department, I presume), had to create Leanback framework largely from scratch instead of relying on official RecyclerView components.
How distracting is it to play a specific song on a radio from 1999? Or a specific FM radio station that isn't already programmed?
This is a silly argument, given the number of arguments that I’ve seen drivers participate in.
even voice can be distracting when you have to repeat variations of the same command five times and keep checking whether it actually works.
I hope this kind of thing doesn't get banned entirely. when it works, I find that having a good navigation system allows me to pay more attention on actually driving the car.