Comments on post “Kuoll JavaScript Tracer”
Andrei Baklinau
@andrei_baklinau · Growth Hacker (Fxclub.org), Blogger
Hey guys!
It's very interesting product.
Do you have competitors in this space? And what is your killer feature (s)?
Btw, can you provide some examples of how your current users / clients get value from your product?
5sharetweet・
Dmitry Kaigorodov
@kuolldev · ceo/founder, www.kuoll.com
@andrei_baklinau Thanks for your questions.
= Do you have competitors in this space? =
Sure, there are tools for developers that catch JavaScript errors and save them to a server.
There are also tools that record user sessions. Most of them are for marketers.
FullStory is quite widely used by developers, but it is still a visual playback tool.
Kuoll is more like a flight black box recorder that records all the technical information and makes it available when necessary.
= And what is your killer feature (s)? =
The killer features are
1) authentic user session browser internals state replay,
2) cause-effect chains to find the root cause of a problem,
3) offline recording stores the record in the end user web browser. And sends the record to server only when the exception, server error, user support request happens.
= Real-life examples =
A banking software company releases a new product. Banking-accounting merged to deliver simpler service for small businesses. Their customer, a flower-shop owner submits a form online. Suddenly, there is a glitch. The owner call to the bank to solve the problem. But customer support engineer starts asking many question. Asks to send a screenshot, install screen-sharing software...
After this, developer gets an issue report that does not have sufficient information to understand the reason of a bug. Developer needs to recreate environment and reproduce the issue. Even after this, developer is not sure if the cause of the issue is the same. With Kuoll, complete browser state is recorded and available to the developer when necessary.
4sharetweet・