Time to Stable

For a given set of browsers, what APIs are in all of them and how many days it take for the API to land in the first browser to the last.

Summary

Average time for an API to become available across Chrome, Firefox, Safari, and Edge

60 APIs took an average of 385.33 days to become available to use.

API breakdown:

• WebAssembly: 385.33 days

Average time to landing by year of first landing

The Tortoise and the Hare

There is a natural tension on the web with respect to browser engines. Every engine has their own set of priorities which define the level of investment that they choose to make and on which areas they choose to make it.

A developer naturally wants their experiences to be available to the widest audience possible and these differing priorities create an unevenness on the platform (a lumpiness) making it harder for developers to build experiences that work everywhere.

This section highlights where browsers are pushing and pulling on the platform.

Sprinters

This table is designed to show which browsers are pushing on the platform the most.

Adding features to quickly is not always desired because developers are unlikely to adopt those features in their sites or apps.

Plodders

This table is designed to show which browsers are pulling on the platform the most.

Stable APIs

Below is a list of features that are in Chrome, Firefox, Safari, and Edge

Raw Data

• WebAssembly

WebAssembly Data