4 ms·
And thus, the whole web gets IAP’s.
by teddyh 6y ago
And thus, the whole web gets IAP’s.
- fouric 6y ago...which is much better than the current state of the web, which is "(nearly) everything is funded by advertisements".
- teddyh 6y agoPossibly. But I remember the time of Shareware, especially on the Amiga platform. It seemed that every little itty-bitty utility program on the Amiga cost some small amount of money. Meanwhile, all the popular programs on PC (DOS and Windows) and Unix (Sun etc.) were mostly GNU-style free software, and guess who won that development? I’m worried that the entire currently-free web will stagnate by all web sites feeling forced to adopt this pay-by-the-click model. However, you are certainly right in that the current ad-supported model is driving engagement, or, should I say, “enragement” clicks, which is certainly not doing much good.
- pedrokost 6y agoThis sounds great. Instead of trusting each company to implement their own billing system with some payment processor, just have the payment processors and banks provide "apps" that support these protocols, and users can chose which one to use to complete their payment. One interesting follow up question in who covers the processing fee (e.g. the ~3% or so that Braintree or Paypal currently take)? Today, processing fees are mostly hidden to the user. If the user can chose their own payment processor, will they be required to cover the processing fee instead of the merchant?
- teddyh 6y ago> Instead of trusting each company to implement their own billing system with some payment processor, just have the payment processors and banks provide "apps" that support these protocols To me, this sounds dangerously close to the argument for the W3C standardization of DRM in the browser. I remain wary.
- chrismorgan 6y agoNot from this. This is for sending money (the push model I speak of in another comment here); in-app purchases are apps demanding money (the pull model) and getting confirmation. For IAPs, you have the Payment Request API: https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API https://developer.mozilla.org/en-US/docs/Web/API/Payment_Req...
- teddyh 6y agoI don’t see the conceptual difference. Could one not describe the HTML (containing a payto: link, delivered to a web browser), as a “push”, and a subsequent click on that link as a “confirmation”?
- chrismorgan 6y agoClicking on the link doesn’t do anything. It might open a banking app, where the user could make the suggested payment, or perhaps alter it, or perhaps not do it after all.