3 ms·
This is a perfect example of a line having to be drawn somewhere, but wherever you draw it is never going to be perfect in every case. First of all -- app stor
by crazygringo 5y ago
This is a perfect example of a line having to be drawn somewhere, but wherever you draw it is never going to be perfect in every case.
First of all -- app stores need to make money or at least break even. They cost a lot of money to run. So app stores take a cut of all transactions. If they let developers implement their own payment mechanisms, either in-app or with a single link, then developers will make every app free, with a link to their own payment, and the app store now becomes unsustainable and we're back to the same malware problems that plagued early versions of Windows.
At the same, there are legitimate use cases where an app is just one facet of a whole service, and so the app store lets users consume content purchased elsewhere, just not buy it directly -- see e.g. Kindle, etc.
Now how is an app store going to draw the line? Well an easy rule is: prohibit any information about payment, and prohibit a link to any page that has a link to make a payment or talks about making payments.
It's a pretty reasonable rule. So in this case, the developer had a link to a page that at the bottom has a link to make a payment. Not allowed.
Sure the developer can argue the reviewer had to "scroll to the very bottom of the page" but it doesn't matter. It's on the page. And then they say the reviewer had to "click through twice to find a way to contribute funds" but that's false -- clicking through twice is just part of the payment process. The main page already has direct links to Patreon and for PayPal.
Would it be nice if Google could add a subrule that links are allowed if they're at the very bottom of the page? Well how do you even define that, what if the page is a single sentence and then payment options? Or a rule that "donations" are allowed? Well then you get "donations" that come with "bonus functionality" and so forth, and a new line has to be drawn.
So is this annoying for the creator? Absolutely. But is Google hugely in the wrong? It's not perfect, but they had to make some kind of rule and the one they've got is pretty decent. Can the creator do anything about it? Yeah -- they can just link to a page on their website that doesn't contain donate buttons. It's really easy. Or else allow donations in-app but allow the app store to take their cut, which goes towards hosting, distribution and discovery of the app anyways.
- Borgz 5y agoGoogle already allows/requires tax-exempt donations to not be done with Google Play billing. This doesn't apply in the case of this app because the developer is supposedly an individual rather than a non-profit organization. >Or a rule that "donations" are allowed? Well then you get "donations" that come with "bonus functionality" and so forth, and a new line has to be drawn. There really isn't any ambiguity about what constitutes a donation. If you receive something in return, it isn't a donation. I would argue that Google could easily permit donations of any kind at no detriment to themselves.
- anticensor 5y agoWhy do they forbid tax exempt donations through Google Play billing? I would instead require everything including physical goods to be paid through them, and apply double cut to donations (kidding indeed, I am not a narcissist).
- mkishi 5y agoThe thing about this app is that they don't advertise donations anywhere, and people aren't donating for the app, they are donating for the content — and that's available everywhere. You know, the same criteria that Apple uses to distinguish Kindle and Dropbox from non-content-reader apps. The service Google provides is the Play Store, and it'd be extremely reasonable for everyone to pay for it. We aren't entitled to that for free. On the other hand, a cut of all transactions? How about a flat baseline fee for platform development plus usage-based fees for everything else, from bandwidth to support? But then they wouldn't be able to double dip on users and app developers... Plus, they so kindly give you so much exposure on a platform built themselves! You wouldn't expect to rent a place in Times Square and not pay for it with a percentage of your income, right?
- zestyping 5y agoThere's no reason for this to be the only solution. This doesn't have to be the only revenue channel for Google, or even the only revenue channel for an app store, and even if it is the revenue channel for the app store, this doesn't have to be the method of making people use it. > Would it be nice if Google could add a subrule that links are allowed if they're at the very bottom of the page? Well how do you even define that, what if the page is a single sentence and then payment options? Or a rule that "donations" are allowed? Well then you get "donations" that come with "bonus functionality" and so forth, and a new line has to be drawn. You're leading yourself down a garden path here. To break even, an app store only needs to take in enough to cover its hosting and traffic costs. It doesn't have to take a cut of all transactions.
- MrStonedOne 5y ago> First of all -- app stores need to make money or at least break even. No, they don't. The moment google and apple designed their phone os to favor the official app store over 3rd party, they lost the ability to make this argument. > They cost a lot of money to run. So app stores take a cut of all transactions. If they let developers implement their own payment mechanisms, either in-app or with a single link, then developers will make every app free, with a link to their own payment, and the app store now becomes unsustainable and we're back to the same malware problems that plagued early versions of Windows. They could make the dev pay for this directly, rather then take a cut. cost per-download plus cost per-review and failed appeal could cut this down dramatically. They also don't get to push their business decisions on to devs that want access to device users. Google decided to make the phone favor their app store, google decided to drive more users to only use and trust their app store. Google decided to use restricted apis to do this. Google decided to have google play protect trigger virus warnings on any 3rd party installed app. They made the business decision to do those things to the phone OS to disfavor 3rd party app stores, and i think the moment they did so, they stopped having a right to run the play store at a profit or even at break even, and they definitely stopped having a right to demand a cut on all of an apps profits.
- deleted 5y ago[deleted]