I already have the desktop app, what difference should this even make? Pointless gatekeeping by the devs

  • Greg Clarke@lemmy.ca
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    22
    ·
    edit-2
    11 months ago

    Pointless gatekeeping by the devs

    More likely it’s to ensure that you’ve actually listened to the podcast you’re rating

    edit: Can someone explain the downvotes, what am I missing here?

    • skuzz@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      2
      ·
      11 months ago

      It’s easy for the service to know if the user account has listened to the podcast, and equally easy to track listens in a webapp. The line between webapp and app is very thin these days anyway.

      • Greg Clarke@lemmy.ca
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        3
        ·
        11 months ago

        The line between webapp and app is very thin these days anyway.

        While the user experience may be similar (and in many cases is identical) access to device information is different. For instance, a webapp can not determine the devices volume whereas an Android app can. Device APIs can provide much more confidence that an activity has occurred. I doubt this was an arbitrary decision or gate-keeping by the developers.

    • intensely_human@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      I’d say you’re getting downvotes because it’s not a design standard to block rating access based on confirming someone’s consumed content.