Thanks for the post @kwdinc Hi, fellow hunters! We created Kuoll as a JavaScript tracing development tool to help JavaScript and web developers fix bugs extremely easy. We are developers ourselves (of course) and we know how difficult it is to analyze and fix production bugs. Here are just some of our features: user session recording, network XHR recording proxy, cause-effect tracing, offline recording. The tool is still continuously developing. In the coming months, we’re planning to add a Summary Report, and Issue Tracking Integrations. Please, share your feedback and your ideas. It will help make the product even better. Thank you for trying Kuoll out =) Dmitry Kaigorodov, CEO/co-founder

@kuolldev @kwdinc is it similar to webvisor from yandex?

Thanks for asking, @alexander_chekan. @kwdinc Webvisor is a tool for marketers that visually replays user sessions. It is used mostly to optimize landing pages and forms. Kuoll-recorded user sessions are actually debuggable. So, a developer has the original record of the assigned problem/issue. Also, Kuoll records both visual and non-visual interactions. Including network requests, user-generated events and javascript promises/callbacks, so that developers do not need to reproduce issues to analyze them. To summarize, we are different as we are a tool for developers to fix bugs.

@nedudi Thank you!

@kiryl_a_anoshka Thank you! We will keep working hard!

@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.

@sridhar_kondoji Hi, thank you for your question! The free account is limited to 50 sessions per month, but you can try Team account for free for 30 days. Using Team account you have unlimited sessions per month, unlimited users of team account and 180 days session lifetime!

@petrbrzek Never tested, but would love to try it with some existing application.

@kuolldev @petrbrzek Have an Electron App. Currently, I am using Sentry to collect crash reports. I'll try this out over the weekend with Electron. One of the biggest problems I have with Sentry is that it's not that good in giving me enough information on regards to the crash.

@td_evans Wow, great! Would love to hear your feedback. Btw, my email is dmitry@kuoll.com.

@m_arbesfeld Thank you!

@gijo_varghese Would love to hear your feedback!

@svifi Thanks for the questions. -- Is it limited to certain JavaScript frameworks? No, it is not limited to certain Javascript frameworks. -- How about server-side JavaScript? It is definitely in our plans. Now we can show requests/responses from the server.