2 ms·
> The alternative to [x] [is] looking at my phone. This is the biggest failure I see in a lot of car apps. Spotify and VLC both limit what I can scroll through
by godelski 4y ago
> The alternative to [x] [is] looking at my phone.
This is the biggest failure I see in a lot of car apps. Spotify and VLC both limit what I can scroll through when scrolling through my libraries on my media screen. Being alphabetical I could scroll through a lot without looking, but they truncate it. All this does is cause me to disconnect my phone, open the app, search, and plug it back in. When the failure mode is significantly more dangerous than the "safety feature" being created, your app is dangerous.
There are so many good intentions that do not consider the failure modes. Yes, there is voice alternatives, but people still don't like using those. I know there are app designers here, PLEASE PLEASE think about how your apps fail! Sometimes the cure is worse than the disease. Good ideas and clever designs can still fail in spectacular ways. You cannot ignore your failure analysis. Dogfood your apps. Make your friends eat it too and be honest. Figure out what they do when things fail. Driving apps aren't your run of the mill smartphone app where you can "move fast and break things," they are apps where failures can lead to people crashing and getting injured or worse. You have to come from an (physical) engineering perspective rather than a software perspective. I'm amazed that even big names frequently get these designs wrong (e.g. the above Android Auto complaint).