I think the only way to make progress on this (or any other similar device-specific issues where Chrome is different to an APK) is:
- Make the most minimal project you can that demonstrates a performance difference between Chrome and APK, with on-screen performance measurements
- Export both to the web and as an APK
- File an issue with Google at crbug.com and include:
- Report "Performance difference between Chrome and Android WebView on <device>" (refer to the APK as the "Android WebView", since that's what Google call it)
- Links to both the web version and APK
- Steps to reproduce in both cases and observed measurements
- Details about the specific device model (in this case Doogee N20)
I'm only speculating about what the problems may be (it's just experience has shown GPU drivers are usually the culprit in this type of thing). If you can get Google to look in to it, they should have the development tools and engineers to work out what the problem really is, and hopefully solve it.
Hi Ashley,
I raised it with Chrome team. Interestingly they directed me to a similar issue which was raised by the Construct developers, which implies that WebView is causing an issue for a lot of people.
This is the issue raised by Construct team.
bugs.chromium.org/p/chromium/issues/detail