In short
- Definition: The ability of a system to run correctly on the required operating systems, browsers, devices and hardware.
- Goal: Reach users on all the platforms they actually use.
- Example S.M.A.R.T. requirement: 100% of critical tests passing on the latest two versions of Chrome, Safari, Firefox and Edge, on iOS and Android.
1. Definition
As a non-functional requirement, platform compatibility describes the ability of a system to run correctly on the operating systems, browsers, devices and hardware its users actually have [1], [2], [3].
“Works on my machine” is not a support matrix.Key takeaway
The requirement is usually written as a support matrix: which versions of which browsers, operating systems and devices are supported, at which level (full, partial, best effort), and for how long.
Platform compatibility is a moving target: browsers update every few weeks, mobile operating systems every year, and old devices stay in use far longer than expected.
2. Goal
The goal is to reach users on all the platforms they really use, with a consistent experience.
Unsupported platforms mean broken screens, lost customers and support tickets, often from the users who can least afford new devices.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Critical tests passing per supported platform | % | 100% | Automated cross-browser and device testing |
| Share of real traffic on supported platforms | % | ≥ 95% | Analytics |
| Platform-specific defects open | Count | 0 critical | Defect tracker |
| Time to support a new OS or browser version | Days after release | < 30 | Release notes |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Web application: “100% of critical end-to-end tests shall pass on the latest two versions of Chrome, Safari, Firefox and Edge, on desktop, iOS and Android, before each release.”
- Mobile app: “The app shall support iOS and Android versions used by at least 95% of active users, reviewed every quarter.”
- Desktop: “The client shall run on Windows 11 and on the two latest major macOS versions.”
5. Questions to Ask Stakeholders
- Which platforms do current and target users use?
- What share of users may be left unsupported?
- How long must older versions be supported?
- Are there corporate standard devices or browsers?
- Which features may degrade on older platforms?
- How will platform testing be automated?
6. Common Pitfalls
- Testing only the developers’ browser. Use a device and browser matrix based on real analytics.
- Never updating the matrix. Review it regularly as platforms evolve.
- Relying on non-standard features. Use standard web features and check browser support before adopting new ones.
7. Related NFRs
- Compatibility — coexisting with other software and versions.
- Portability — moving to different platforms.
- Accessibility — assistive technologies differ by platform.
- Environmental Protection — supporting older devices extends their useful life.
8. FAQ
A list of supported platforms and versions, with the level of support for each.
A common rule is the latest two versions of major browsers, adjusted to your real audience.
With cloud device and browser farms running end-to-end tests on each supported combination.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [4] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [5] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [3] |
| OS | Operating system | Core software that runs a computer or phone, such as Windows, macOS, Linux, Android or iOS. | [6] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Cloud | Computing resources (servers, storage, services) rented over the internet from a provider. | [7] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [8] |
10. Sources and Further Reading
- [1] “Cross-browser compatibility.” Wikipedia. https://en.wikipedia.org/wiki/Cross-browser_compatibility (accessed Nov. 18, 2026).
- [2] “Computing platform.” Wikipedia. https://en.wikipedia.org/wiki/Computing_platform (accessed Nov. 18, 2026).
- [3] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [4] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [5] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [6] “Operating system.” Wikipedia. https://en.wikipedia.org/wiki/Operating_system (accessed Nov. 19, 2026).
- [7] “Cloud computing.” Wikipedia. https://en.wikipedia.org/wiki/Cloud_computing (accessed Nov. 19, 2026).
- [8] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @firmbee; inline photo by @laurenmancke, both on Unsplash.




