• Tzig@sh.itjust.works
      link
      fedilink
      arrow-up
      25
      ·
      1 year ago

      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

      • Irdial@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        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.

      • Spectacle8011@lemmy.comfysnug.space
        link
        fedilink
        arrow-up
        2
        arrow-down
        3
        ·
        1 year ago

        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”?