By Alexandra Levich, Product Manager
Cross-posted from the Chromium Blog
We recently expanded the reach of the Chrome Web Store from the U.S. to 24 more countries. Developers from around the world have already launched successful apps in the Chrome Web Store to US users. Now all developers can reach a global user base.
What makes this global reach even more interesting is the global payments infrastructure that goes along with it. The store allows developers from 20 countries to sell apps in the store, and users to buy apps in their local currency. We also recently launched the In-App Payments API, which allows developers (U.S.-only for now; international soon) to sell virtual goods in their apps. Integration is easy and transaction fees are only 5%. Graphicly, an early user of in-app payments, saw its net revenues double after starting to use the API and experienced an even bigger rise in profit margins due to increased conversions and lower transaction fees.
In keeping with our international theme, we’d like to highlight a few developers from different parts of the world who have utilized Chrome’s global reach to find success in the store:
- Audiotool is an online music production app that was built by a team of German developers. They saw the Chrome Web Store as a way to present their app to an international audience. Audiotool’s traffic increased by 20% after launching in the store, and this motivated the team to release another app in the store.
- Psykopaint is the brainchild of French developer Mathieu Gosselin. The Chrome Web Store provided Mathieu an opportunity to get his photo painting app noticed outside of France. Traffic to Psykopaint has jumped by 700% since it launched in the store and Mathieu has found that Chrome Web Store users tend to be more engaged than other users.
- Finally, Nulab, a Japanese company, launched its online diagramming app, Cacoo, in the store to expand its user base outside Japan. In just a few months after Cacoo was released in multiple languages in the Chrome Web Store, the app already accounts for 20% of Cacoo’s user base.
The experience of Audiotool, Psykopaint and Nulab shows that no matter where you’re located, you can always find a global audience for your applications in the Chrome Web Store. To learn more about the stories of these and other successful Chrome Web Store developers, read our case studies. And if you want to find out more about posting your app in the store, visit our documentation at code.google.com/chrome/webstore.
Alex Levich is a product manager working on Chrome Web Store.
Posted by Scott Knaster, Editor
Kabam was part of the initial launch of Google+ Games with two game titles, Dragons of Atlantis and Edgeworld, and we recently added Global Warfare. For these games, we integrated Google In-App Payments and we’re pleased with our games’ monetization to date. There are a couple things we learned along the way that we’re happy to share with the community.
Integrating In-App Payments
Integrating In-App Payments in our games was very simple, especially when compared to other payment platforms. There is excellent documentation available, complete with examples for each step of the purchase flow. We also used open-source libraries such as ruby-jwt to generate the tokens required for each purchase option.
We designed our games and purchase pages around the expectation of instant feedback, making sure to incorporate page loads or refreshes wherever possible. For example, in Edgeworld, a player attacking an enemy base can load the list of Platinum options instantly, without waiting for the list of payment options to load. After their Platinum purchase, the player is immediately brought back to the game, with their new currency and items waiting for them.
Pro tip: strive to reduce purchaser friction
One of the keys to maximizing revenue is to remove as much friction as possible from the purchase flow, making sure as many people as possible get from one step of the flow to the next. Many payment platforms send players to their own website and multi-page checkout flow. The Google In-App Payments approach allows us to keep players on our game page for the entire flow, making sure we can manage more of the process and reduce abandonment.
Last year, the Google DevFest Tour gathered thousands of developers collectively around the world. Attendees heard from peers in the community already running their businesses on the Google platform. Googlers working on various Google developer products and APIs were on hand to talk about the latest and greatest, with best practices on how to improve the quality of web and mobile apps.
To continue giving you the opportunity to interact with us and get feedback, we’ve decided to announce another tour, in addition to the recently announced Google Developer Days. We’ve updated the 2011 DevFest site with tour cities and dates. We will continue to update the site with more detailed information such as venue location, agenda, and registration.
Please remember that space is limited at each location. We cannot guarantee that everyone will be able to secure a spot. We highly recommended you register early and check back for event updates. We’ll email confirmations, which you can then use as your tickets to these events.
Blogger rolled out some nice new stuff this week. It’s different inside and out. As a heavy user of Blogger (you’re soaking in it!), I’m happy with anything that helps us make a better blog for you to read. If you have a Blogger blog of your own, here are a couple of the changes you’ll notice:
- Each settings page has a button that starts a new post. Creating posts is what bloggers do most, and now you always can get to the post editor with one click.
- You can see traffic and other stats in one place. The new Overview page shows you page views, comment activity, follower counts, and more.
For more information on what’s new in Blogger, and to find out how to turn on the new features, see this Blogger Buzz post.
Adding features to software is hard enough. Bumping celestial bodies around is another matter entirely. Hexi Baoyin of Tsinghua University has suggested giving a gentle shove to an asteroid so that it ends up in Earth orbit.
Google are releasing two new versions of the Google Analytics Management API into public beta: a brand new version 3.0 and a backwards compatible version 2.4. Both new versions migrate the Management API from the existing Google Data Protocol to Google’s new discovery-based API infrastructure. This impacts the way you request and handle data from the API.
All future development of the API will be done to version 3.0, so we also added some interesting new data, including:
- Event goals are fully represented.
- An internal web property id that can be used to deep-link into the Google Analytics user interface.
- Profile configurations for the default page and site search query parameters.
With this change, we are also announcing the deprecation of the legacy version 2.3 of the Management API. It will continue to work for 2 months, after which all v2.3 requests will return a v2.4 response.
The biggest changes in switching to the new versions are that you now need to register your applications via the Google APIs Console and use a developer token. Also, the URL endpoints have changed, which influence how you request OAuth authorization tokens.
For complete details on what’s new, see today’s post on the Google Analytics Blog. If you have any questions or concerns, please join the conversation in our Management API developer group.