View Single Post
Old 10-29-2012, 04:55 PM   #15
hbtaylor
Enthusiast
hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!hbtaylor My eyes! My eyes! The light is just too bright!
 
Posts: 32
Karma: 80378
Join Date: Nov 2011
Device: iPad 3, Nexus 7 (2013)
Quote:
Originally Posted by murraypaul View Post
Edit: Oh, and yes, apps sold through Google Play must use Google's APIs for any in-app purchases, for which Google take 30%. I think the same is true for Amazon. I think the application is of a less blanket nature than Apple's restrictions though, which apply to all content.
The big difference is that Google doesn't preclude, for example, the Amazon app from having a "Store" button that goes through a separate purchase mechanism. Sure, Google offers in in-app purchase framework and takes a cut if you use it. But app developers aren't required to use it. That makes buying books in the Android Kindle app way more seamless ("less seamful"?) than in the iPad Kindle app. For the iPad I have to switch over to the browser myself, or to wherever I have a shortcut to the store site, and switch back to the Kindle app when finished. On Android I tap "Store", then choose "Home" from the menu when finished.

I don't begrudge Apple for charging for use of their in-app purchasing. What does bother me is forcing companies with have fully-formed store/purchase infrastructures to use the Apple one.
hbtaylor is offline   Reply With Quote