2 ms·

So, iOS is supposed to start supporting alternative payment providers, so that apps can start using them without those apps seeing any update, but only for dati

So, iOS is supposed to start supporting alternative payment providers, so that apps can start using them without those apps seeing any update, but only for dating apps, and only in the Netherlands? Would it have to work if a user installs multiple dating apps, and picks different payment providers for each of them, changes them a few times a month, etc? How would users configure payment providers (presumably in iOS settings, as the apps can’t be changed)? I don’t see how iOS could come preloaded with every payment provider on the planet (if only because new ones can pop up every minute), so should it download and run code that processes the user’s money, or would Apple be allowed to restrict what payment providers can do so that iOS can configure them based on a few items (say an icon, a descriptive text, a background image, and some info on how to make a payment)? I can see solutions here, but not ones that can be implemented in a few weeks time. Implementing such a feature takes time, even if you can throw money at it.

jeroenhd 5y ago
Payment is easy, you can use regular old webviews to handle payment. You don't need native payment providers to be supported at all. The Dutch iDeal system easily integrates into apps as well through banking apps. Callback URLs are well supported and any app can register protocol handlers for them to receive confirmation of payment (which the app then must verify through a backend API call, to prevent abuse, of course). This is all quite trivial to implement, and requires no work from Apple at all. The specificity is because of the nature of the lawsuit. A bunch of dating apps decided to join forces and sue Apple in the Netherlands. The judge ruled against Apple, so Apple has to allow the dating apps (and probably the entire dating category) to use alternate payment options. Sure, going by the law Apple should probably allow all apps in Europe to use alternate payment options, but Apple is making more money than the noncompliance fines. They're trying to bleed anyone enforcing the law dry by pretending to do what was asked but in the most detestable, childish, and stubborn way possible. I hope the judge will add a couple of zeroes to these fines because another fifty million is nothing but the cost of business for a company like Apple.

jeroenhd 5y ago

Payment is easy, you can use regular old webviews to handle payment. You don't need native payment providers to be supported at all. The Dutch iDeal system easily integrates into apps as well through banking apps. Callback URLs are well supported and any app can register protocol handlers for them to receive confirmation of payment (which the app then must verify through a backend API call, to prevent abuse, of course). This is all quite trivial to implement, and requires no work from Apple at all. The specificity is because of the nature of the lawsuit. A bunch of dating apps decided to join forces and sue Apple in the Netherlands. The judge ruled against Apple, so Apple has to allow the dating apps (and probably the entire dating category) to use alternate payment options. Sure, going by the law Apple should probably allow all apps in Europe to use alternate payment options, but Apple is making more money than the noncompliance fines. They're trying to bleed anyone enforcing the law dry by pretending to do what was asked but in the most detestable, childish, and stubborn way possible. I hope the judge will add a couple of zeroes to these fines because another fifty million is nothing but the cost of business for a company like Apple.