Since this thread is about Crosswalk experiences, I'd like to share mine. I had given up on Crosswalk almost a year ago for mobile development, but just yesterday I gave it a chance, just to see if it might work better than CocoonJS Canvas+ now that it's been some time. I was impressed with how far the Intel XDK had come. The interface seemed a little more intuitive and it was easier to get a build. But once I tested the .apk, I immediately started laughing, in a cynical, horrible way.
My first thoughts were: What a joke! Not only did my compiled game stay stuck for 5 minutes with the C2 loader, but once it loaded, the game was pixely. It was rendering at a lower resolution. On top of that, it was slow and janky. So not only did it fail to perform as well as Canvas+ fps-wise, but it introduced new graphical and loading issues that made it far worse. It was laughable. It did even worse than it had done when I tested it a year or so ago.
Now that it's a been a day or two and I've recovered from the agony of the situation, and considering that people have claimed to use Crosswalk successfully for their games, I'm going to give it the benefit of the doubt and assume I screwed up the configuration somewhere. But yeah, that's my story. I'm going to stick to CJS Canvas+ for now.