Live data from Hacker News

What Apple Pay Could Mean for In-App Purchases

markokarppinen.com

11–20 of 42 posts

Re: What Apple Pay Could Mean for In-App Purchases

#11
"The 30% IAP cut equals billions of dollars in yearly revenue. But being in this commission business is not in Apple’s DNA."

I would say it is entirely in Apple's DNA. Apple has aggressively tried to inject themselves between sellers and buyers in multiple markets, even where their value add is unwanted and unnecessary.

And I don't fault them at all for that. They're a business and they're doing what businesses do, growing revenue. Trying to get a pound of flesh from the payment industry process is something many players are aggressively trying to do right now, and Apple is no exception.

And of course in the end all fees end up being borne by consumers.

One fallacy that many make in such discussions is the argument that Apple makes so much from hardware they really don't care about the smaller parts of their business, yet they have shown that they care very much about it. Don't think of Apple (or Google, or Microsoft, or any other growth company) as a $N billion dollar company -- every day they are, to the people fighting for more market, a $0 company, because all that matters to the tiers and people involved is $(M-N) tomorrow.

Re: What Apple Pay Could Mean for In-App Purchases

#12
post #11

"The 30% IAP cut equals billions of dollars in yearly revenue. But being in this commission business is not in Apple’s DNA." I would say it is entirely in Apple's DNA. Apple has aggressively tried to inject themselves between sellers and buyers in multiple markets, even where their value add is unwanted and unnecessary. And I don't fault them at all for that. They're a business and they're doing what businesses do, g…

One reason why I suspect Apple could be different in this regard is the fact that they famously have only a single P&L. So whereas in other companies divisions and the SVPs running them would jealously guard every piece of revenue that was rightfully theirs, Apple as an organization could be better equipped to avoid that — if deemed beneficial to the overall business.

Re: What Apple Pay Could Mean for In-App Purchases

#13

The Appstore revenue is dwarfed by hardware sales, with all of Appstore/iTunes revenue being less than 10% of iOS hardware sales. Apple certainly doesn't NEED the 30%, but it's very doubtful they'd reduce it.

I would guess that the profit margin on IAP is higher than on hardware.

How much does it cost to maintain the servers and infrastructure associated with IAP vs. the cost of building hardware?

Re: What Apple Pay Could Mean for In-App Purchases

#15
The reason that the friction argument is bullshit is that Apple forces you to use their system. If their system truly was better, (higher conversion) then they could reasonably explain this to the people they charge.

Another reason that 30% is BS is that it leaves no room for low margin sales. If I make an app that helps you find and buy the right computer monitor or TV, I'd have to mark it up 25% in order to break even after Apple takes it's cut.

Re: What Apple Pay Could Mean for In-App Purchases

#17
I see ApplePay and Google Wallet as the Virtualization of payment, basically turning your credit card accounts into electronic accounts with per-device and per-payment tokens. Which means that security will be a lot easier, numbers can't get stolen, and the merchant now doesn't AUTOMATICALLY get your info from your credit card, while retaining the ability to track you (probably) as long as the Payment Processors allow it.

HOWEVER! It also means that these companies will need to integrate their new payment system deeper and make it compete with IAP on their own ecosystem. Since this system disrupts credit cards for real world purchases, it can't take a 30% cut. So you end up with two systems of payment, one which takes 30% and one which doesn't. You can bet your buttocks that publishers of online content will try to find ways to use the CREDIT CARD PROCESSING system instead of IAP, even if it means no fancy things like recurring subscriptions - things which ApplePay will have to add later. In short, Apple will have to bend over backwards to justify preserving the 30% cut on IAP. That 30% incidentally is also what keeps all apps from being free in the store - once IAP is cheap, why charge people 30% upfront for the app?

In short, I'm interested to see how Apple is able to keep ApplePay from cannibalizing its revenue from the App Store, by disrupting its own IAP service.

Re: What Apple Pay Could Mean for In-App Purchases

#19
post #2

He is wrong. In fact Apple charges the banks: http://www.bloomberg.com/news/2014-09-10/apple-said-to-reap-... Which makes sense, when you read the technical details published earlier today here on HN: http://clover-developers.blogspot.de/2014/09/apple-pay.html

Banks make money from credit cards by * charging a % from each transaction * late fees * interest on balances This assumes banks make less money on transaction fees than they do on the other two when coupled with the potential for fraud... An interesting assumption...

Is this how it works? My assumption was that Mastercard, Visa, American Express, and Discover were the ones that made the % of each transaction and then the issuing banks were the ones that made the money from fees and interest.

Re: What Apple Pay Could Mean for In-App Purchases

#20
post #11

"The 30% IAP cut equals billions of dollars in yearly revenue. But being in this commission business is not in Apple’s DNA." I would say it is entirely in Apple's DNA. Apple has aggressively tried to inject themselves between sellers and buyers in multiple markets, even where their value add is unwanted and unnecessary. And I don't fault them at all for that. They're a business and they're doing what businesses do, g…

The 30% as far as I understand is roughly covering the cost of running the app store. I.e. huge revenue but not really much profit.
Post reply on HN