Browser and OS Support Policy

[nothingismagick]

We can't demand from users that they always update their operating systems. There are valid reasons for not doing this, as in mobile-phone lockout where the vendor prevents system updates, or specific software for which someone has a license, and it just won't run on a higher version of MacOS or iOS. This is not specifically safe, but also something we aren't in a position to dictate entirely. I propose that we allow any OS currently in LTS where security updates are still being performed. (As in Windows XP is out of scope.)

The same can not be said of browsers. In fact, this is why we are creating native apps in the first place. Browsers get updated all the time. If people are using browsers to interact with our platform, they NEED to keep the browser current, and not just because we say so. It is integral to their safety on the internet. Zero-days are constantly being uncovered, patched and released - these are the so-called "Security Updates".

Therefore, I suggest we support the following set of browsers:

• Chrome
• Firefox
• Edge
• Safari
• Mobile Safari (upon which all iOS webview apps are based)
• Android Webview (if things work as they should in Android Chrome // Firefox, great)

There are tons of browsers and edge-cases. I suggest we create a noscript, no-cookies version of the site - perhaps cached as monolithic page-renders from a post-update hook that uses the ´$ quasar prod´ service and generates them with phantomjs (also installed in the repo via npm, for example). Of course with languages this gets tricky - and maybe we need to revist our canonical domain description to include the language in the stub, but we should first discuss this.