GrapheneOS, a privacy-focused version of Android, is adding Android Auto support - eviltoast
  • saegiru@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    10 months ago

    The main argument I have against just phone + bluetooth is that you have to unlock your screen, keep it on, and it’s a smaller size. I have wireless android auto set up, along with a magsafe case+charger, so my routine is to get in the car, slap the phone on the charger, and everything just comes up on my head unit display. For me it is way more convenient than having to deal with my phone display, and the larger screen is also better for navigation.

    I have yet to hear any real negative points against AA or CarPlay for that matter, mostly it comes down to preferences like yours rather than actual interface issues.

    • BrianTheeBiscuiteer@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      I vaguely remember one of my cars supporting AA and I disabled it because I saw no benefit. Either it’s not very intuitive or the apps I prefer to use don’t integrate with AA.

      • saegiru@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        I am not sure how it could be much more intuitive, at least from a touch screen perspective. It’s just a touch interface with an app drawer, nothing much more to it than that. However, if it wasn’t a touch screen I could believe it not being very nice to use, as I have a friend that has an Audi that does CarPlay but the screen isn’t touch, so he had to use physical buttons to use the interface. THAT is definitely not good.

        As for the apps, I use Signal, WhatsApp, Messages, Spotify, YT Music, Waze, and Google Maps and they all support AA, so at least for my purposes it does what I need from a car apps interface standpoint.