Browser Support

Last Updated: 11/01/2019

This statement describes the current status of the support process from design to deployment. Expect this statement will adjust over time with changes in technology and project goals.

Browser Support Statement

We strive to support^[1] an ever-widening set of target^[2] platforms as is feasibly possible—with respect to project goals.

While developers strive to produce bug-free code on all platforms, if a bug exist on a non-supported target^[2], developers will attempt to address them on a case-by-case basis as determined by the developers and project goals.

The goal is to support^[1] the latest (and previous) version of the following browsers on a rolling basis. Each time a new version is released, the project begins supporting that version and stops supporting the third most recent version.

TL;DR

• Support means "We've tested browsers x, y and z against our criteria and it passed the tests."
• Support does not mean "We expect it work work in x, y and z."

Target

Currently supported browsers.

Target²: Currently Supported Browsers

VERSION	IE11	Edge	Firefox	Firefox Android	Chrome	Chrome iOS	Chrome Android	Safari	Safari iOS
latest	🚫	✅	✅	🚫	✅	⌛️	✅	✅	✅
latest -1	🚫	⌛️	✅	🚫	✅	⌛️	⌛️	⌛️	⌛️
legacy	🚫	🚫	🚫	🚫	🚫	🚫	🚫	🚫	🚫

• ✅: Supported Target
• ⌛️: Future Target
• 🚫: Not Supported

Future Target

These are tentative.

These are targets that require additional resources in order to support.

Future Target: (Tentative)

These are targets that we will need to dedicate additional resources in order to support.

VERSION	IE	Edge	Firefox	Chrome	Safari	Safari iOS	Chrome Android	Android Browser
latest	✅	✅	✅	✅	✅	✅	✅	✅
latest-1	✅	✅	✅	✅	✅	✅	✅	✅
legacy	🚫	🚫	🚫	🚫	🚫	🚫	🚫	🚫

• ✅: Supported Target
• ⌛️: Future Target
• 🚫: Not Supported

All browsers must have cookies and JavaScript enabled, certain features may require localStorage and geolocation that must be allowed by the user to enable full-featured experiences.

Footnotes

What Support means

• Actively design for the target from concept, planning through to release
• Actively develop to optimize the experience for the targets
• Actively QA the functionality on the target
• QA Process does not result in a "FAIL", out of 3 possible results
  • PASS: Feature adequately implements the design spec
  • MVP: Feature implements a core MVP experience
  • FAIL: Feature is unusable
    • QA FAIL states result in bug fixes
    • QA MVP state improvements will be remedied on a case-by-case basis.

Non-Supported Targets

If the target is not on this list, that does not mean that it does not work. Non-supported means that we do not actively test against the platform.

• If a certain functionality/design is required to be supported on a non-supported target, it will be done on a case-by-case basis
• No guarantee of exact visual or performance characteristics, but strive to balance the best experience possible for the widest feasible set of targets
• Strive to fully support all other browsers on a case-by-case basis
• Strive to deliver a progressively more hi-fidelity experience based on platform abilities

References

• Influenced by Google statement on browser support.