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.
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.
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.
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.
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.
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.
Afaik that only applies if the app is processing payments, which in this case it shouldnt be.
A lesser standard still applies if it either embeds or redirects to a payment page. Again, shouldn’t mean shit, but still.