• Chozo@fedia.io
    link
    fedilink
    arrow-up
    1
    arrow-down
    7
    ·
    2 months ago

    Why should I know? I’m not a McDeveloper.

    If I had to guess, I’d assume it’s because there’s a payment system in their app and they don’t want people monkeying around with it and stealing food.

    • Ghoelian@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      10
      ·
      2 months ago

      McDonald’s was just an example, the point is most apps don’t need to do that at all.

      I do happen to know how payment systems like that work, and thankfully those are all cloud-based, the only thing the app does is start transactions and check with the server if they’re paid. If they implemented it well, as I suspect a big corpo like McDonald’s probably would, their own order screen also checks server-side if orders are paid. Not much you can do from the app side to mess with that.

      • ℍ𝕂-𝟞𝟝
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        2 months ago

        the only thing the app does is start transactions and check with the server if they’re paid

        Yeah, but the whole PCI DSS thing means that the app must still be secured. That doesn’t necessarily mean that it has to be tied to Google Play, but explain it to them.

          • ℍ𝕂-𝟞𝟝
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 months ago

            A lesser standard still applies if it either embeds or redirects to a payment page. Again, shouldn’t mean shit, but still.

    • sunzu2@thebrainbin.org
      link
      fedilink
      arrow-up
      1
      arrow-down
      4
      ·
      2 months ago

      🤡

      If apps like fidelity will run on aurora store withithout safety net and other bullshit, then shiti McDonalds app can take the risk too.

      You are poorly educated on the iseue or a bootlicker