What's the difference between FullStory Dev Tools and Chrome DevTools?
If you've used developer tools in your browser, such as Chrome DevTools, then some of the features in Dev Tools by FullStory should seem relatively familiar.
Both Chrome DevTools and FullStory Dev Tools give you the ability to view the Console and see a waterfall-style breakdown of Network Requests in a Network Tab.
There are some key differences:
- FullStory Dev Tools allows you to see Console and Network details for sessions as they occurred for real users, in real environments, either in realtime or in the past; Chrome DevTools allows you to debug and emulate environments in realtime but it doesn't give you the ability to see what the session looked like for another real user at a past point in time.
- Because FullStory Dev Tools depends on the FullStory recording snippet loading on a page, some initial network requests may only have partial or inferred data; Chrome DevTools can give you more visibility into the details for the initial requests that happen as a page loads, before the FullStory recording snippet might begin recording.
- Beyond just the Console and the Network tabs, Chrome Dev Tools gives you the ability to view Elements, Sources, Performance, Memory, Application, Security, and Audits.
It's important to remember that Dev Tools by FullStory isn't designed to replace Chrome DevTools or any other developer tools you may use in your favorite web browser. Rather, the magic of FullStory Dev Tools is that it gives you some of the rich details you'd expect from your favorite browser debugging toolkits alongside the visual context of a customer's real experience, brought to life with pixel-perfect playback.