Google I/O 2012 - Ten Things Game Developers Should Know

Dan Galpin, Ian Lewis

This session reveals the things experienced game developers do to get good Google Play reviews, create a strong Android user experience, and be considered for featuring in Google Play Apps.

[Donivar]

Seriously, this is extremely helpful. One of the things developers tend to forget is "put yourself in your customer's shoes". In this video you see why that is important and well, there are a lot more facts too, this is just one of them in this video.

[PublicObjectGames]

If anyone is wondering and didn't search for it... the item number 6 refers to the Bruces sketch by Monty Python (which is why the Australian members of the team didn't like it very much :)).

[Computerfreak]

56:50 "Did you enjoy this presentation? Your five-star rating will help us keep making great presentations like this. Rate us five starts now!"

Oh that's a crack up!

[AchwaqKhalid]

an other thing before i forget, @GoogleDevelopers you really need guys to ask those developers to use the external SD card to store expansion files, since the internal storage is so limited and gets quickly saturated, it's really frustrating! 3 or 4 games with over 1 Gigabyte of additional content each and you will find yourself running out of space, why do we then buy those 32/64 SD cards, the only game that i know do this so far is "The Bard's Tale" by: @Inxile_Ent.

[k.]

this will help me a lot ! thx google dev team

[narucy]

55:15 - "Korea loves android" funny and nice advice!

[markusa.]

Great Talk!
Love the part starting at 36:34: "POINT 8! ... Awesome! ... In-App Payments ... are unfortunately easy to get wrong!"
In fact, it's SO easy to get wrong that the Billing API team at Google themselves screwed it up when building API v3!!!
It's funny that they specifically mention that "[a] lot of people have multiple devices!" (40:43) and then don't get this scenario right in their own APIs...
And even better at 42:37: "Let's leave aside the fact that actually some developers will acknowledge the billing message anyway without successfully delivering it... ahh... those guys just need to get their act together...". That's EXACTLY what the new API V3 docs SAY to do by suggesting to consume a consumable product before successfully delivering it.
The sad part (and the reason I'm posting here) is that I still have not been able to contact anyone at Google about these issues... I couldn't even post it to the respective Android Google-Group for some reason (just never heard back regarding the submission)... Maybe someone will see it here...

would be great to have a summary, could someone?

[AchwaqKhalid]

Not to mention also bad coding habits made on purpose or not like: the app is constantly jumping into memory even after closing it which causes major stability issues due to it Read/Writing in a poor performance card, even a class 10 SD card will be brought to it's knees when you have 5 apps installed like that which at the end will result in the battery not lasting enough, so who should we blame?!!

[narucy]

21:45 - These bad permissions requested to Android OS should display BIG BOLD RED FONT WARNING MESSAGE. Android must be more secure hardly manage permissions.

[MsSomeonenew]

So right off the bat they are advising developers kill all backwards hardware and software compatibility... these guys are pretty much the main reason half of Android shit doesn't work on user devices.

[sacredgeometry]

Ah its not crackling in the bits I care about so it doesnt matter

[victornoagbodji]

umm, the back button thing has many points but the whole could be summarized with "use common sense"... in my opinion : )

[PapiDelPNW]

These guys try to hard to be funny. This presentation could of been cut much shorter, so much bloat information. Android>Bloatware.

[ThNob]

This platform sucks as much as the presentation itself.