One thing I'm really appreciating is how fast I get a result back from Puppeteer (CF Browser Rendering).

The video uses the most trivial example (pun intended), but there's only a few extra secs on top of what the page took to load.

Will this be the case with 00s of users? Would love to find out!

One of the core concepts on Dashboards is that they are fully customizable.

You can copy and paste any widgets from docs and it works seamlessly.

You can share these with stakeholders/colleagues and make sure you're all focusing on the same view (and not getting distracted by noise).

Here's an example on quickly prototyping a change and measuring the before/after in just a few minutes.

Am I missing lots of audits/widgets? Yes.

But I'm mostly missing a few more folks who don't mind helping me with *candid* feedback and/or see themselves using it!

Let me know if that's you! 🫵

2. MEASURE. Run "opinionless" tests.

Pulls CrUX + PSI + Puppeteer (for user journeys with Chrome DevTools Recorder). Run multiple tests to see variability or multiple pages to compare one another.

You can build (and share) your own dashboards. Made plenty of widgets but the more the merrier!

Emil's course (animations.dev) is one of the best resources I've seen on successfully pushing great & practical animations/interactions to production

I'm not personally using Motion but I still got a LOT of insights and tips.

And I'm having a lot of fun humbly using some of those on my own work!

Not sure if this is a good idea (or a terrible one!) but Canvas and WebRTC APIs are pretty great!

TBC on how accurate (this is PSI's Lighthouse, should also be compat with CF Workers Puppeteer and probably more accurate but screencasts have a weird gamma offset unfortunately).