However, keep in mind that depending on the license you have, you may have limitations (eg. The personnal license lets you make up to 5000$ as an individual, the personnal license can also be used by startups that have less than 5000 $ in their total earnings, look up the details of the license you have to know the limits as my description may be not accurate enough.)

I had that audio troubles too, but that webview+ is AWESOME, my physics game has even better performance than with canvas+, why scirra still not officially support it? I heard that canvas+ is not good, but if i understand it right the webview+ is apple system's webview, phonegap using it too, but cocoonjs is even better (because cocoonjs using the WKWebView instead of UIWebView).

Could I ask a question, I though that webview+, and canvas+ are actually working with the html5 export itself, is that so?

If so, official support from scirra of webview+ itself is actually not adding anything, and that would also mean that it would still work long term wise, as webviews are real browser engines (which scirra supports).

I posted on my phone, so forgot the "compliant", I understood it was not OS running in javascript (not that it could not be done, but that is not the point).

I am not really into OS architecture, so I am not sure I understood your post, but if it is a OS Where the graphic interface is not just an addition where you still need using the command line manually, but really a part of it, then as an end user, I like this choice)

I think the specification got finalised recently, not sûre if that means what I think it means, but IMO it means rules are now correctly defined, so I would expect less breaks.

However I understand your frustration.

HTML5 is the future BECAUSE it is truly multiplatform and that everyone can potentially do an interpreter, an ecosystem ruled by rules so you Can rely on others, instead of reinventing the wheel.

as I said before, browsers are just a partial part of its ecosystem, browsers currently failing never means it is impossible, it just means we have to make them try harder to correct the issues.

bugs have to be corrected, never to be worked around, and html5, css, and JS are part of a specification, not a "browser language", if we cannot make it work somehow, it would simply means that we cannot make an entire ecosystem agree on rules, which is more worrying than anything else.

as for the jerkiness, if they cannot vsync properly, then they will have to do another way.

Last time I checked, it was because of the offline.appcache file, safari has issues with sound files and caching it seems.

I think Ashley reported it to Safari developpers.

I also find that suspicious...

First: all the platforms listed, natively, without break, in beta, with all those features listed... either scam or promesses that will not be fulfilled, or will take a lot of time to fulfill.

Second: HTML5, Flash, and natives, what is wrong with them? sounds like "OMG WE HAVE EVERITHIN", first: if they have html5, they already have multiplatform, ok, for some reason they could prefer native I'll admit, but flash..? Flash? Flash? pointless.

"The spark editor has been made with spark": would love to see if it works really in a browser then, also "has been made", I though it was beta.

Scripting + behaviors + events sheets

Last time I saw an editor combining events and scripting, everyone went for the scripting when the events were not working, thus bugs were never corrected.

Use powerful physics: would love to see that working in a browser too, just to see.

Maybe legit, but seems more like ideas....

last time I heard of someone testing this approach, there were differences between the android and regular html5 export, resuting in this particular result in crosswalk, to try out how it performs performances wise, you can test it in chrome for android as the result should be similar as the exported to crosswalk version.

I can see that being useful for, let's say, mod writing or text-based level editing.

Yeah I don't think you're ever going to get a reliable way to auto-detect and change settings during gameplay - provide an option and maybe use the framerate of the first level to set a default and then leave it.

I may add that If the refresh rate is 30, or 50, or 120 (all units in Hz, of course), the result may be adjusted in consequences (not saying it is a bad idea, just reminding that 60 fps is applicable only to a 60 Hz refresh rate, and so caution is still required with auto detection).

Also auto detection is far from being future proof, standards refresh rates may vary in the future, and others things considered "true by default" may also change, and to comment the first suggestion of OS sniffing, it is the bad idea by excellence, could be compared to the browser sniffing used by a lot of webdeveloppers, which caused trouble, headaches, and forced browser vendors to add filthier workarounds. (Why is there even a Is on mobile condition in C2, why, why, why)

AFAIK in other browsers, you cannot curenttly force it (as they did not yet implement this feature), you could detect if it is portrait or landscape, depending on the result, suggesting to the user to rotate their device for a better experience.

Also not all smartphones (I think) have a keyboard that covers the entire screen on landscape mode.