>
> >
> >
> > Any issues you run into with XDK will likely exist with any other web-based exporter, because you don't have control over it, and if you're doing anything it's not expecting the build will fail. The idea that Scirra will be able to provide better maintenance than Intel? What makes you even think that's possible, given the resources of each company?
> >
> > If you want the option to optimize your builds as much as possible, you're better off installing node.js, cordova, java & GIT on your local machine and compiling locally, which takes much less time and doesn't require uploading your assets to a 3rd-party server (that may potentially be unreliable), which is going to be configured to support a more generalized build as opposed to something specifically for your game projects. Reliability aside, if you're working on a bigger project, uploading over even a fast connection adds a lot to the build time - whether you're using Cocoon, XDK or Phonegap.
> >
> > Once set up locally, Cordova isn't difficult to use, and just requires a few command-line options or your setting up a batch (.bat) file when you want to compile. If you're interested in doing this, install in this order: java, GIT, node.js, then Cordova. Installing Cordova last allows it to set up the connections to the other components automatically and no manual configuration will be necessary. Plugins can be installed from the command line/powershell, and I'm sure there's a GUI-based installer for them as well if you're more comfortable with that after setup.
> >
>
> I just don't believe it's possible to achieve the same performance as Canvas+ does with any exporter/wrapper, none of them seem to disassemble the inner workings and recompile as well, or whatever the hell it does. Would self compiling with a batch file improve performance? And by performance, I obviously mean fps. I don't believe optimising code could improve matters to the point where xdk or a batch file build would ever reach the smooth, fluid gameplay cocoon is providing, but it should.
>
> No, doing the build online or offline is just the same... The performance won't change.
> The performance is only influenced by your code, the engine, the device, and the wrapper.
> Changing build options won't change anything but changing wrappers is another story...
> Changing from IntelXDK to Cocoon.IO or vice versa would change performance.
>
> But finding the best performance wrapper is up to you.
>
No, the performance won't change if the exporters you're trying are all based on PhoneGap/Cordova, that's correct. I was referring to the speed of the build process, not the application that results from it. And as 
Ashley mentioned Canvas+ is a total mess, and non-standard, and performance isn't predictable across hardware because it's non-standard. There's little to "optimize" in terms of the build that's exported that's exporter-specific, other than Canvas+ they're all using pretty much the same backend to build. Canvas+ isn't really doing anything all that much different in terms of the game's overall codebase so if you're seeing drastically better performance using it over WebGL/Cordova export, you're probably doing something wrong. It's not doing what you think it does.
Well I've had perfect performance with canvas+ and unacceptable performance with xdk and phonegap, so what could I be doing wrong to gain such a boost in performance?