Can anyone explain in detail what this means for us? I'm curious if this just impacts things like ads and IAP. Or will this also help with some of the larger issues like audio problems, 9patch/tiled bg support, perf, etc.

They claim bug fixes and improved performance, so its up to you to test your game and see if its fixed.

Otherwise, the only major thing is the inclusion of Google Play features.

Well I assumed the point of putting this on github was basically "your problem now". So it would be up to us to fix things going forward, but I'm curious how tied into the platform the plugin is. Will working on it impact things like support for our objects and audio, or is that really something that can only be fixed internally in the cocoonjs code.

firebelly - I agree that it's good and bad now that it's been given to give it to the community.

My fail comment was just because Ludei came out with a big positive blog and fanfare: "Today we’re releasing the new CocoonJS Plugin for Construct 2. WOOHOOO!!" After reading that I imagined that it might in fact work and not cause C2 to crash.... If the headline had read "we didn't really test it and, to be honest, we had better commercially driven things to be getting on with - so, there you go, good riddance to it / what a relief" then my expectations would have been better aligned with reality.

I do think that this will be good in the long run, though - but only if there's someone in the community who has the time, skill and inclination to get in their and tweak the plugin for the greater good. I would love to give it a go but I am useless at coding...