3 ms·
I would expect from a developer's perspective it makes sense to stick with Apple's mechanism until ARR * 0.30 = whatever it costs to run your own solution. (Mor
by eszed 3y ago
I would expect from a developer's perspective it makes sense to stick with Apple's mechanism until ARR * 0.30 = whatever it costs to run your own solution. (More power to you if you're the developer who can do that from the start, but that won't be most people.) I wonder, though, if the slow siphon becomes more obvious if it's attributed, in a customer's credit card statement, to [Game Co.] instead of [APPL]. I won't be sad if fewer people spend money on those types of games.
- MBCook 3y agoI agree for the developer. But there’s the cost of users who don’t want to go outside Apple that you’d need to account for. And right now we don’t know how big (or small) that effect is.
- lttlrck 3y agoExactly. - no need to enter a CC number in another site (and maintain it) - no need to create another account to make that payment (or unironically use Apple Pay flows) - trivial cancellation - trivial cancellation of limited time trials Maybe I'm fortunate, stupid, or a combination but not being able to pay for Netflix using Apple subscriptions really bugs me and I'd pay more to avoid it. Which reminds me I need to cancel it...
- saynay 3y agoDepending on the developer, there is also quite a lot of trust I need to impart on them too. I am reasonably confident in Apple keeping my data secure. I would likely be confident in it for the bigger apps out there, like your Netflix or Spotifys. But some rando app, would I be comfortable putting my personal and financial info on their server, instead of just using Apple's?