In the past, I've been asked to support customer developers to understand performance problems the are seeing in their instances.
There are plenty of articles out there that talk about a variety of techniques, tools and best practices. I've written one or two myself.
I wanted to take a brief look at the Next Experience Developer Tools Chrome extension, to see what it brings to the table, and who might benefit from installing, understanding, and using it.
The docs page describes how it can be downloaded from the chrome store, because It's a chrome browser extension. Once installed, I can open the browsers developer tools panel and see the Next Exp options have been added. I'm ready to go.
Reading the docs, and after spending just a few minutes working through the extension, it's clear that most of the capabilities in NED are firmly intended for pro coders. Experienced web developers, UI/UX Designers who are building applications leveraging the next experience UI. It is of value too, to especially keen system administrators but realistically you do need a strong web development background to get the most out of it.
If that's you, you'll most likely spend more time working through the capabilities available as part of the Inspector than I did. There, you have access to tabs which show things like the page components, events fired by components, traces, logs.
What I found more interesting was the Service Workers info, and the Profiler.
In the profiler, performance snapshots are captured and can be locked to the loading of a page.
You can then compare a previously taken snapshot, from one taken later - perhaps having made a change to try and address a performance bottleneck.
Docs for the Next Experience Developer Tools can be found here, or perhaps more usefully directly from the chrome extension itself.
1 Comment
