Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple and Google must allow other in-app payment systems, Korean law declares

theverge.com

Post reply on HN
Print view View original

141–150 of 627 posts

Re: Apple and Google must allow other in-app payment systems, Korean law declares

#141

Post by WA »

MDWolinski wrote: post #78

I'm wondering how this will eventually play out if most companies start requiring Apple/Google to allow third-party apps to use their own payment system. The commission fee that Apple charges, 30% is partially to cover operating/marketing etc. Obviously, Apple makes a good profit off the App Store these days, even though Jobs said he'd be happy if it was break even at best. Here's an analogy I've been thinking on abo…

> The commission fee that Apple charges, 30% is partially to cover operating/marketing etc.

Then by all means, please charge me separately for these things. Because I don’t need them. Apple doesn’t do marketing for me, never promoted my app. People find my app through my own marketing channels.

Charge me roughly 2 % for In App Purchases just like Stripe and PayPal.

Charge me a traffic fee for whatever download traffic I cause. This way, I at least benefit from my app being only like 5 MB in size.

If I want to be featured on the App Store, charge me.

The rest like App Store listing? Covered by my $100 developer fee.

Re: Apple and Google must allow other in-app payment systems, Korean law declares

#142

Post by commoner »

mrtksn wrote: post #129
yobbo wrote: post #66

Earlier quoted context omitted.

> I despise platform fragmentations It is fair to point out that "platform fragmentation" occurs because of the policies of Apple and Google, not because of regulation. If they had some altruistic care for user/dev experience, the platforms would be open and frictionless to begin with. Their aim is to insert friction at all points of interoperability, and remove friction inside of their own platform.

Nothing is altruistic. It's simply business and business is about to get harder for smaller developers.

Smaller developers now have more payment processing options in South Korea. In addition to Apple's and Google's own systems, they can also choose from a wide variety of third-party systems that charge ~3% instead of 15%/30%. I don't see how this would be anything but a benefit for smaller developers.

Re: Apple and Google must allow other in-app payment systems, Korean law declares

#144

Post by cblconfederate »

pcr910303 wrote: post #103

It’s not usual for news on my country to be on top of HN. Very unexpected. I’m guessing though that the South Korean market is be significant enough for Apple and Google to not just pull out it’s business from South Korea and call it a day. I guess this is, in some kind, a victory against the huge companies. But… personally I do find sad that this would be detrimental to South Korean app UX. Stripe isn’t a thing here…

Traction brings improvement over time. SV companies enjoy enormous first mover advantage and megaphone that pushes their products to the masses early to capture them, and then iterate on UX.

Re: Apple and Google must allow other in-app payment systems, Korean law declares

#146

Post by mrtksn »

commoner wrote: post #136
mrtksn wrote: post #124

Earlier quoted context omitted.

Obviously everyone can do whatever they like, I am pointing out the burden this puts on smaller developers. Suddenly, creating and distributing apps can get prohibitive for smaller developers.

> Suddenly, creating and distributing apps can get prohibitive for smaller developers. That's not true, because the law does not prohibit developers from using Apple's or Google's current payment systems. It enables more payment processing options (with lower fees) without removing existing ones. Developers can also choose different payment processors for different regions.

It means that if those payment processors gain market share from Apple I will need to support them to reach the exact same userbase because if the users adopt using the alternatives it is very likely that they will stop bothering to upkeep their Apple payment methods. It happens all the time and there's even API for it to offer the users a grace period until they fix their payment.

Re: Apple and Google must allow other in-app payment systems, Korean law declares

#147

Post by hyperionplays »

jaywalk wrote: post #107
Hnrobert42 wrote: post #92

Earlier quoted context omitted.

What do you mean “without having to pay”? Google pays for its connection to the internet, right?

No, in most cases they don't.

This. Google has amazingly helpful peering bilats with most major ISP's globally, they don't have to pay for transit nearly as much as the rest of us. they were a staunch defender of net neutrality because it let them avoid millions of $$ in transit.

Re: Apple and Google must allow other in-app payment systems, Korean law declares

#148

Post by sumedh »

ubermonkey wrote: post #105
sumedh wrote: post #94

Earlier quoted context omitted.

> If you want your product to be sold in Walmart No one is forcing you to go through Walmart. The problem with IOS is that you are forced to go through Apple. A user cannot pay, download and install the app directly from a developers website.

Nobody is forcing you to sell to iOS, though.

That argument does not work when there are only two service providers in town, Apple and Google.

Re: Apple and Google must allow other in-app payment systems, Korean law declares

#149

Post by [deleted] »

pcr910303 wrote: post #103

It’s not usual for news on my country to be on top of HN. Very unexpected. I’m guessing though that the South Korean market is be significant enough for Apple and Google to not just pull out it’s business from South Korea and call it a day. I guess this is, in some kind, a victory against the huge companies. But… personally I do find sad that this would be detrimental to South Korean app UX. Stripe isn’t a thing here…

[deleted]

Re: Apple and Google must allow other in-app payment systems, Korean law declares

#150

Post by simondotau »

Dracophoenix wrote: post #134
seanalltogether wrote: post #93

Earlier quoted context omitted.

Should I pay Apple for the right to build a Mac app, or Windows for using their desktop apis? Maybe I should have to pay mozilla and google every time someone visiting my website and I use a piece of javascript that executes in their browsers?

Historically, people had to buy developer tools like compilers and assemblers for hundreds if not thousands of dollars either directly from the company or through retail channels if they wanted access to the inner workings of their computer. Apple included. So the pay-to-build model isn't new. As far as what "should" happen is concerned, that'll be a matter of debate and contract law if/when Apple changes its terms a…

Indeed. And Apple does have the benefit of prior art in the case of games consoles which have—for the past 30 years at least—required developers to accept some kind of revenue share for the right to distribute software to customers.
Post reply on HN