It is fairly OK in terms of the compatibility across Apple products - as always for the ecosystem. However, the way it works is totally poor - when the apps is closed (either by user or somehow killed by iOS) the airplay connection drops. In opposite, content played by chromecast seems to sustain individually, regardless of the apps status.

Even I am using iPhone and have an Apple computer at home, a chromecast hardware is installed and more frequently used than Airplay.

Do anyone else experience similar as me?

  • Independent-Bear-604@alien.topOPB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Sometimes when I do a lot of multi-tasking, the app is killed by iOS. A possible flaw could be from the app itself, but the logic behind airplay also plays a key part.

    • _mikedotcom@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Wild that in 2023 you have to explain that you want to multitask on an iPhone and getting downvoted for it.

    • autokiller677@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      It is most definitely a problem of the app. I have never seen an app actively playing media being terminated by iOS. That’s really disruptive for the user, and Apple usually protects the user experience from stuff like this. But do to this, the app has to correctly communicate to iOS that it is actively playing media.

      The upside of AirPlay is that it works with everything. Chromecast needs to be supported by the service you want to cast so the phone can hand off the connection to the Chromecast (something that AirPlay can actually also do, at least for video). But if an app / service does not support it, using the device as a streaming relay is the only way to enable casting of basically everything.