Google I/O 2013 - In-App Billing Version 3

[@FlameQuantum]

I really like your presentation. Very smart and humorous. Great presentation!

[@hosseinmahdavi3164]

Can you create a traning about implrment in-app purchasing with google API

[@gauravmeghanathi]

I have an question how to maintain user record with different account in android app with their server . with current subscription i have an app with facebook/app sign in on a server to maintain thier record to sync with thier mail (facebook email/ app emial id)

[@twinjuke]

Can I find some information about what's the average percent of in-app purchases versus the total number of downloads for an android app?

[@necromancer151]

ALSO PLEASE ADD memo field in market web ui

[@fabiodaddario]

How can i get informations about the app purchase?

[@necromancer151]

Implementing sandbox a good move ( for a 5 years of in app billing) next step i think would be do the same but without actual sign of app or put it into google play for test

[@Neurochrom]

So this presentation is a case study on how NOT to design an API?

[@necromancer151]

Guys! ADD server callback from GOOGLE platform! NOT clients!

[@KangJangkrik]

build official in-app billing plugin for adobe air please...

[@markusa.9931]

The v3 API and this talk as well as the current official documentation have some SERIOUS logic flaws: One is fairly obvious and can be easily fixed: At 15:26 he says to first consume the product and only once the consumption succeeded should the item be credited to the user. What if the app crashes after consumption is completed by Google Play but before the app is done crediting the product to the user? (Continue at 5:58 for what happens then...) Fixing this is straight forward: BEFORE consuming the item, remember somewhere in non-volatile storage, that you are about to consume the product and need to credit it to the user... Done... Now, the much bigger problem is that the new "all products are managed"-policy is fundamentally incompatible with supporting a single user account across multiple devices! The easiest way to see this is: What happens if a user buys a potion on his TABLET and the app crashes after purchase but before consumption. This happened at 4:15am and the user decides that he was tired anyways and goes to bed instead of re-openening the app. Next morning, he turns on his PHONE and opens the game to play on the train on the way to work. The app checks for owned products: "Oh! There's a potion! Awesome! Credit! Consume!" So, the product will be credited to the user on the WRONG device! Now, this can be fixed by adding a device-id to the developer payload so the phone knows to ignore the purchase made on the tablet, but (as explained at 13:17) this will prevent the user from buying another potion on his PHONE until the purchase is consumed on the TABLET. Worst case scenario: The app crashed because the user dropped his phone in the pool and the device broke. Now, the purchase will NEVER be completed and the user will NEVER be able to buy another potion on ANY of his devices... Fail... For a more detailed description, and a quite hacky attempt at solving this, you can check out my StackOverflow question regarding this matter: stackoverflow.com/questions/30921789/working-around-api-purchase-logic-flaws-for-consumables-in-google-plays-billing Unfortunately I still have not been able to reach anyone at Google about this issue... But maybe this post here will be read? Feel free to pass this on if you have a way to do so and are concerned about this as well.

[@tuxjsmith]

I am attempting to add In-app billing to a new application. Trouble is, your presentation has very little in common with: purchase-iab-products.html and that page seems to have little relation to this one: billing_integrate.html The 'helper' classes seem to represent that bunch of salad you show on your first few slides :-)

[@manibabuankireddy24365]

how to manage subscriptions means downgrade/upgrade in android

[@roshansebastian1862]

If you got the code for managing subscriptions or anything that helps a developer for managing subscriptions later, can you share it ?

[@tali676]

No entiendo todo lo que dices. Puedes crear otro en español

[@adirmugrabi]

9:10 "the planet gets to win..." unless this phone is an old nokia Phone. in that case, the earth will shatter

[@testymctester7542]

The real joke is the IAB implementation + that ridiculously bad sample code! The jokes are seriously infuriating when dealing with this mess... for shame

[@Callum15121990]

Sup?