Predicted future Baseline status?

[LeaVerou]

This may well be out of scope but I figured I'd propose it in case.

Often, a piece of data that is useful in addition to current browser compatibility of a feature is its future compatibility. This could be incredibly useful for teams making decisions on whether to depend on a given web platform feature. For example, for a new product or a new version of an existing product that is going to be released in e.g. a year, what matters is not what is Baseline now, but what will be then. Obviously, most teams are not on the cutting edge and even Baseline 2025 is too early for them, but for certain features (e.g. those that can be used in a PE fashion) it can be a useful piece of data.

At this point we have enough data to predict this pretty accurately once a feature ships across the board.

[atopal]

This is indeed part of our roadmap for this year:

Ensure Web Features can represent nuance that is needed for decision making by web developers by providing information about upcoming changes (additions and removals) and notes

I could have sworn we already had an issue for this, but all I could find was #955. I do agree that there should be other indicators as well, for example inclusion in Interop.

[foolip]

I recall @jgraham talking about a forward-looking aspect while we were working on the Baseline definition. I agree this would be very useful. We could predict it based on beta data in BCD a few weeks or at most months ahead of time. It's also reasonable to assume that features in https://wpt.fyi/interop-2025 will in fact be shipped, most likely during 2025. Beyond that any kind of "we fully intend to ship this" signal from browser vendors could be used.