Yeah, using the webview for games is a big handicap. Even the simplest of games can lag, especially since worker mode isn't supported in the webivew.
We have like 3 issues:
1. Browsers are extremely slow on mobile.
2. Event sheet's overhead.
3. Stutters, I'm guessing from no worker mode.
Since #3 might get supported in the future, that's probably not a hopeless issue. #2 can be ignored if #1 hopefully gets better.
Although, in my opinion, it's not Construct 3's fault, I'm surprised how efficient the runtime is, given the handicap.
But yeah, we're stuck with browser limits. Even Cocoon.io gave up. 😅
I think the Webview is more suited for simple games that doesn't do anything much.
Perhaps we overestimated the engine's performance? Might be more practical to target simpler games?
Although, I would appreciate if the Construct Team did something to finally solve this issue. 🙂