It depends on what you need. If you are happy with chrome/chromium's developer tools (for example for memory monitoring) you can use them with nw.js too.

Here's a little explanation on how to get them:

https://github.com/nwjs/nw.js/wiki/debu ... h-devtools

If you are looking for something like the Unity profiler for in-depth rendering analysis, I don't have an answer.

Works here on Android. The controls feel super unresponsive on mobile, but the parallax background works.

What devices/OS revisions did you test on?

At some point, Ashley implemented a 30fps-mode, because of public demand. It died in the same Beta-cycle and never reached stable, because it didn't work right with web tech. It caused a lot of problems, so the idea was abandoned.

For the last part: custom icons have to be added manually at this point.

You have to edit the "resources" of the exe-file (that's something like metadata in the header).

There are tools to do this, for example an old and trusty tool called "Resource Hacker".

All of those "grid style" games like tetris, match3 etc. can be made without arrays and purely "reactive". The problem is, that this gets really bad to maintain really quickly.

Doing it without the abstraction is not really easier. It's easy for some blocks falling down, but as soon as it gets interesting, you want arrays.

Layers have a property called "Global" that you can set.

If you do so, it will be in every layout, and you don't need to copy. There are a few things to be careful about, so best check the global-layer-section of the manual, too.

Have you tried with today's beta? (r222). There was a workaround in place which led to periodic blips or static on some configs, and it has been removed in the latest release.

Steam Controller only registers as a Gamepad when used to launch a game via Steam through Big Picture mode.

Has this worked for you with a C2 game? (Because for me it has not, would be curious what you did)

Right now the browser gamepad api seems to only like xbox 360 (and compatible) pads.

With all others, all bets are off. It's pure luck if they work.

— have you tried the suggested solution for the lingering dead nw.js apps? (rename the project and/or get rid of old data folders)

Because I don't seem to get them anymore when making a completely new project.

It shouldn't (imho).

I often need to register input on objects that have no collision. The one thing is totally independent of the other and should not be mixed.

Someone had it working at some point, using XDK I believe.

But seriously. Ouya has been dead for like 2 years now. And its performance was always too weak to deal with wrapped HTML5 games.

Have you tried to load one of your APKs with it?