When a newcomer is asked to work on a front-end application they know nothing about, it's really hard for them to understand what code is executed when and why and where it originated from, while they are looking at the code or playing around the application as a user.

Trakk.js allows newcomers to easily get onboarded on the applications they will be asked to work on, by providing them with a nice, clean and very informative UI about what "event" took place, where in the code, when and why, just by simply playing around with and testing the application in real-time.

Trakk.js allows you to easily and automatically generate documentation regarding the whole of your application's flow. What code was executed when, where and why and because of which user interaction with the page. A newcomer can go through that documentation and study it or use it as a reference point during their onboarding.

As a Front-End Application increases in size, it gets harder and harder to debug your code. It's hard to track what function is called when, where and why. Same for Server Requests, Uncaught Errors & User Actions. Relying solely on breakpoints on your browser's devtools or debugger statements and console.logs in your code can become cumbersome.

Trakk.js provides you a nice, clean and very informative UI about what "event" (function, request, error or user action) took place, where in your code, when and why.

You, the Developer of the application, or the Tester, wants to play around with the application and make sure that all the right code is executed at the right place and at the right time and for the right reasons.

Trakk.js allows you to do that by providing you with a nice, clean and very informative UI about what "event" took place, where in your code, when and why.

Writing documentation is hard. Especially for large-scale applications that keep evolving and changing. It's easy to leave things out and it's even easier for documentation to become outdated.

Trakk.js allows you to generate documentation describing the whole of your application's flow, the complete code journey combined with all user interactions (and screenshots) that took place at every point of the way. With a single click of a button, every time your application is updated, you can then quickly generate new, accurate, up-to-date, documentation describing in detail everything that took place in your newly updated application flow. Because the documentation is generated automatically based on all code execution that took place, it is impossible for it to leave things out or document outdated content.