Yikes.<p>As far as I can tell, the only meaningful thing this adds is the ability to require developer registration in order to use experimental APIs.<p>&gt; The ultimate goal is to enable experimentation and iteration on pre-standardization APIs, in a way that gathers meaningful feedback, but without burn-in of the APIs.<p>I&#x27;m not sure what&#x27;s broken about the &quot;experimental&quot; label except that it can&#x27;t trace usage back to specific developers. If it&#x27;s experimental, it will probably break or disappear. &quot;Burn-in&quot; doesn&#x27;t have to be a problem if you <i>actually</i> iterate and yank or change stuff. API keys don&#x27;t solve anything that code removal doesn&#x27;t solve (aside from developer tracking).<p>Want to curb &quot;developer abuse&quot; of vendor prefixes? Remove the API. Train developers to understand that experimental features are experimental by actually following through. If you don&#x27;t want users to think the browser is at fault, maybe alert the user to that fact. &quot;Oops, looks like this website&#x27;s developers were a bit careless with their code. Sorry about that; some people like to take big risks and it stinks that you the user had to suffer for it.&quot;<p>If you really want to ensure that only specific devs are allowed to use some features, presumably to limit impact on users and loss of browser market share, then just ship those devs a custom release. Protect usage of the whole browser with a key, if you want.<p>Personally, I&#x27;d rather we leave things open to experimentation (with an established and valid understanding they may break) over locking it down to devs willing to give you their phone number so you actively approach them for feedback and turn off the tap on a per-developer basis if you so desire.