Competitive Dashboards

  • Competitive Dashboards help provide an objective way (although have the potential to be editorialised) of letting developers and ops teams compare different products to see if they meet a bar set out by the author. It can also be an incentive for products and projects on the dashboard to implement critical missing features or meet performance targets... if the dashboard has enough visibility in the ecosystem.
  • Best patterns and practices for creating a competitive dashboard
    • The dashboard is only as useful as the last update, if it's no longer updated it's inaccurate and shouldn't be relied on - unless the "is X ready yet" shows "X is ready".
    • Try not to be the owner of the tool/product/goal and use it to downplay the work of others. The goal is to be as objective and as critical as possible so that developers can trust the output.
    • More coming soon.
  • More links

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.