this post was submitted on 06 Nov 2023
107 points (95.0% liked)
Programming
17364 readers
198 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
CarPlay and Android Auto aren't car OSes though, they're merely an infotainment interface. You still need a way for the user to check the tire pressure, choose between sports mode and eco mode... Cars manufacturers could just implement the basics and let CarPlay/Auto do the rest but in that case anyone that doesn't have a compatible phone is stuck without infotainment, same if you run out of battery.
CarPlay and Auto being so good is somewhat to blame for first party interfaces being that bad though: why spend litteral millions on look and feel if you know the users who care won't be using it
Yes, this is a good point. I think the best way to do it is to have the car controls visible at all times, with the CarPlay/Auto interface wrapped in a frame. This is how Jeep does it.
It's worth mentioning that Android Auto doesn't work on GrapheneOS due to the privileged access it requires, and will not support it unless it is re-architected. Which phones were you thinking of when you said "compatible"?