markwhiting
commented
4 years ago I think an easier option is just to tell people it won't work on mobile. We can also add something on the front end that warns them if they are going on a phone.
Mobile is tricky to design for, especially low-resource devices, which may be doing a lot of things to manage ram and battery usage.
It is possible to debug on a phone (e.g., you should be able to load things on your phone and many browsers have tools to help for that).
Many people report common bugs such as the screen going blank upon moving on from wait chat, or timers going down to 0:00 without moving on to the next screen. I've been asking these people what their system requirements look like (since I have done extensive testing and never encounter these issues), and learned that most people with these instability issues are on mobile.
Is there any way to debug / increase the stability so that people do not experience these issues on mobile?