3 ms·

My point is that Apple doesn't see in-app payments as merely payment processing. They see them as App Store purchases which are delayed in time. Everyone keep

by zach 16y ago

My point is that Apple doesn't see in-app payments as merely payment processing. They see them as App Store purchases which are delayed in time. Everyone keeps anticipating Apple becoming a payment processor, but it hasn't happened yet. They're still a platform provider. This kind of reminds me of some of the TripAdvisor reviews you see on resorts with a championship golf course and all kinds of amenities. There are always people annoyed that because just wanted a simple room and don't want to have to pay for the amenities. They argue they should be able to pay a lower rate. But they just stayed at the wrong place. A 30% rent is a great rate for what the App Store provides, but if all you want to pay for is a better payment processor, yeah, it does seem outrageous.

jaaron 16y ago
No, a payment processor is exactly what they are in this case. Consider what Apple is attempting to do to Amazon's Kindle service: users can purchase Kindle ebooks directly in-app but Apple takes a 30% cut of the payment. Amazon still hosts and provides the content, all Apple does is act like a payment processor like Visa or Paypal. Clearly Apple wants to shove out competition to it's own iBooks, iTunes and movie services.
- zach 16y ago
  And yet there seem to be a lot of books as apps on the App Store considering there's this 30% cut. What kind of inside track should Amazon have on the poor shlubs who sell their books as apps?
  - potatolicious 16y ago
    The poor schlubs who sell their books as apps haven't cut out the middleman. With Kindle (or iBooks), the author simply uploads his/her work in a commonly exchanged format. Everything else is handled - distribution, payment, formatting, device compatibility. The works. As an author who wants to publish their book as a discrete app, suddenly you're engaging with a different middleman - the inevitable app vendor. The vast majority of book authors aren't coders and wouldn't know how to publish an app to save their lives, much less on multiple platforms (Android, iOS, webOS, WP7, along with their phone and tablet variants). Inevitably they will buy this solution (which, in essence, is largely of the same nature as Amazon/Apple) from someone else. And what will we, as consumers, have seen from this situation? More confusion and a worse experience overall, as every single little piece of content now floods the app store, obliterating any sense of discoverability while making the UX much, much worse (downloading a discrete app, along with all of its code and media, every time you want to read a book?!)
    - zach 16y ago
      Bookbaby makes it pretty easy, but I don't see how that even matters. You're just arguing that there should be more middlemen, sub-platform-providers who get a special deal with Apple compared to original app authors. We can all foresee what happens when providing a hammer factory is favored over providing a hammer. It's not good UX or good for consumers.

by zach 16y ago

jaaron 16y ago

No, a payment processor is exactly what they are in this case. Consider what Apple is attempting to do to Amazon's Kindle service: users can purchase Kindle ebooks directly in-app but Apple takes a 30% cut of the payment. Amazon still hosts and provides the content, all Apple does is act like a payment processor like Visa or Paypal. Clearly Apple wants to shove out competition to it's own iBooks, iTunes and movie services.

zach 16y ago
And yet there seem to be a lot of books as apps on the App Store considering there's this 30% cut. What kind of inside track should Amazon have on the poor shlubs who sell their books as apps?
- potatolicious 16y ago
  The poor schlubs who sell their books as apps haven't cut out the middleman. With Kindle (or iBooks), the author simply uploads his/her work in a commonly exchanged format. Everything else is handled - distribution, payment, formatting, device compatibility. The works. As an author who wants to publish their book as a discrete app, suddenly you're engaging with a different middleman - the inevitable app vendor. The vast majority of book authors aren't coders and wouldn't know how to publish an app to save their lives, much less on multiple platforms (Android, iOS, webOS, WP7, along with their phone and tablet variants). Inevitably they will buy this solution (which, in essence, is largely of the same nature as Amazon/Apple) from someone else. And what will we, as consumers, have seen from this situation? More confusion and a worse experience overall, as every single little piece of content now floods the app store, obliterating any sense of discoverability while making the UX much, much worse (downloading a discrete app, along with all of its code and media, every time you want to read a book?!)
  - zach 16y ago
    Bookbaby makes it pretty easy, but I don't see how that even matters. You're just arguing that there should be more middlemen, sub-platform-providers who get a special deal with Apple compared to original app authors. We can all foresee what happens when providing a hammer factory is favored over providing a hammer. It's not good UX or good for consumers.