Amazon's Takes In-App Purchases Out Of Beta: Here's How They Compromised On Revenue Share
Amazon is taking the wraps off a new in-app purchasing service today in an effort to make its app store competitive with what Apple and Google offer developers. That should let developers …
Context & Ripple Effects
Amazon’s Android Appstore entered 2012 with a history of asserting control over paid-app pricing and receiving criticism that the store was underwhelming. The move from beta to a public purchasing service addresses a core developer requirement as Amazon tries to compete for Android software against Apple and Google.
The revenue-share compromise matters because Amazon’s earlier control over paid-app pricing made commercial terms part of its developer proposition, not merely a back-end implementation detail.
First-order effects
- Amazon Appstore developers gain access to Amazon’s in-app purchasing service beyond its beta phase, giving them a platform-native way to sell within apps.
- Amazon can present developers with a monetization tool designed to narrow a product-gap with Apple and Google’s app ecosystems.
Second-order effects
- Amazon’s revenue-share terms become a direct factor in whether developers prioritize its Appstore alongside Apple and Google, rather than treating distribution reach alone as the decision criterion.
- Apple and Google face another Android distribution rival competing on developer economics as well as catalog availability.
Third-order effects
- The rollout points to app stores competing as full monetization platforms, where payment rails, revenue splits, and control of transaction terms shape developer supply.
- If competing stores keep differentiating through commercial terms, developers’ dependence on a single storefront becomes less about publishing access and more about the economics attached to each platform.
The trend: Mobile app distribution is evolving from catalog competition toward competition over the payment systems and revenue-sharing rules that govern developers’ businesses.