Aphrodite
My statement about Canvas accelerated devices was from this facts:
- In my country there are many store sell super cheap low-end new Android phone that have single core, small RAM and weak GPU or maybe even no GPU at all.
- Webview from Android Kitkat 4.4 (also in built-in browser) is suffer from bugs that slowing down Canvas based app (this also affect many Cordova compatible app that using Webview)
http://code.google.com/p/android/issues/detail?id=62641
https://code.google.com/p/chromium/issu ... ?id=315111
- Desktop browser on many PC suffer from blacklisted GPU and also low performance for integrated GPU.
- Today there are many newer devices with better hardware specs but a year ago the conditions is different and rendering CSS3 is faster than Canvas, you can read about it in:
http://www.goodboydigital.com/to-dom-or-not-to-dom/
For 60 fps is Construct standard, i found it at:
https://www.scirra.com/blog/83/optimisa ... -your-time
" Most modern displays update at 60 Hz, so the target of the game is to run at 60 FPS, so each time the display updates there is a new frame of the game to show. If the game runs faster than 60 FPS, there is no visual improvement! "
and
https://www.scirra.com/manual/169/debugger
" Delta-time (dt) is set as if the game were running at 60 FPS. "