From “supported” to a shared baseline
Browser support discussions often collapse into a yes-or-no question even when the real answer depends on browser versions, release timing, and the audience of a product.
Baseline provides a common way to describe when a web feature becomes broadly available across major browser engines. It does not replace product analytics or accessibility testing, but it gives design and engineering teams a more consistent starting point.
How I use it
I treat Baseline as one input alongside usage data, fallback cost, and the value of the feature. A newly available API may be appropriate as progressive enhancement before it is suitable as a hard dependency.
The important improvement is conversational: instead of arguing from remembered compatibility tables, a team can state its support policy and evaluate features against the same reference.