I did recently make a cocoon io project:
https://itunes.apple.com/us/app/humped/ ... 73409?mt=8
then i hit a snag with cocoon io (their plugin database got messed up and i was getting a mysterious black screen that i couldn't get to go away..sooo.. i moved over to xdk to make this one:
https://itunes.apple.com/us/app/smod-th ... 54828?mt=8
I was overall pleased with my return to xdk. I did HATE all the icons you have to submit manually.. Cocoon IO does it all with one graphic. Built times were fast on both. Cocoon IO's still got XDK beat in APK size. Cocoon IO makes APK sizes that are a fraction of XDK's crosswalk.. performance wise I couldn't tell a difference. Both were snappy.
I liked using cocoon's native plugins and it's just nice to not need to rely on unsupported ones like the cranberry ones (Sang Ki is a great guy, he just doesn't have time to address issues promptly) where the cocoon ones are officially supported for C2 so if something isn't working you can bring it up and get some support, though they are not fast when you're a silver or free user.
In my case this time though, I found that admob and google analytics worked with with XDK. Overall I felt fairly 50/50.. though my next game I will start with Cocoon IO and this time hope the black screen problem doesn't come back again. That crap is annoying. I can never really clearly get an answer to what is wrong and why it's doing it.. knowing the nature of the problem could better help me understand where I'm doing something wrong to fix it.. anyway, at this point, I think they are both great. Cocoon IO is better for smaller android apps but frankly I still see android as secondary... and iOS as the main and in both cases iOS apps are small.
Is this with crosswalk or webview? I'd have thought once webview has phased out crosswalk, between the improved apk size, the performance should be as good?