Skip Navigation
24 comments
  • What is so wrong with CarPlay or Android Auto T_T

    • 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"?

  • I worked for a German car company for a little bit, in a team responsible for a similar system: https://www.srcbeat.com/2023/08/sbt/

    • I'd be curious to read more about the context of this. It looks like there are soo many low hanging fruits for anyone with mid-level technical seniority to step in and improve the situation measurably. Scala isn't bad but sbt definitely has plenty of (avoidable in hindsight) footguns. The tooling ecosystem of Scala has also improved leaps and bounds in the last couple years. Of course that doesn't do anything to the seemingly disfunctional organization but like the engineering post it was, it didn't concern itself with it much.

24 comments