I ran into some problems while making a webgame (no multiplayer, just runs in the browser). It looks like some things do not run smooth as soon as the web connection goes below a certain threshold.
For example, it seems to continue loading, even after the loading screen has finished. Or at some point, the game just gets stuck when a tester is using it on their phone in a bad wifi, which I can not reproduce on my working machine with good wifi. I don't think its a performance issue of the phone, because a bad phone with good wifi has no problems, while a good phone with bad wifi does.
My plans are now to throttle my own connection to see at which point the game breaks. But in order to solve the issue and to give advice on the minimum internet connection requirements, I'd like to know more about how a webgame works.
I assumed it would download all data and then run it relatively undisturbed by the further connection. Is this true? Because it seems as if its communicating with the webpage even after the initial download. Otherwise I would not have problems only in bad wifi?!
You see I am stumbling in the dark and would appreciate an answer on how it works in the background and an idea on why bad wifi has an influence although the content of the game should apparently be downloaded to the device.
---
Edit: I think I might be on the issue's tracks. With the offline option, the documentation says: "If you're online and you load the project, the browser loads from disk instantly as before. However, as the project is running, it checks for an update in the background. If you've uploaded a new version, the browser downloads it and saves it to disk. Then, next time you load the project (including refreshing the page), the browser loads the new version. Until then, the user keeps using the old version."
I think that might have been what happened. That the game started on the old data, but then, while already running, downloaded additional data and was not fast enough with the download to display it. Just a theory at the moment though.