 So, I started the Modify seven months back and it's to basically help developers develop the websites and some of the customers, I don't know, just get this straight. So, what is the Modify? It's like Google Analytics for web developers. And what's the need for this kind of a product? So, let's start, let's see how web is evolving. Two years back, if we have this kind of a Gmail, now it's this kind of a Gmail, like all the things are moving from server-side, running code to more of client-side to JavaScript-driven code. And so, as you can see, browsers have evolved a lot in the last two, three years. Over the time, you can see Chrome has a lot of features in the last 22 years. So, as browsers are evolving, a lot of code breaks in JavaScript because all browsers have different APIs for the same functions and different implementations, which can lead to a lot of problems for developers. I think almost everyone of us has faced similar issues. So, and when code breaks, mostly users get frustrated and users get frustrated, they call support and they make them frustrated. And now, time for developers to get frustrated. This is something like, for any product, like release a product, you test it thoroughly and next week or something, some browser upgrades, some library upgrades, your code eventually breaks and most of the time you don't know because most of the testing you have done is of no use, like not that much use. So, and even when something breaks, you are not aware of that because mostly of the problems, error information is captured in the browsers and developers don't have access to much of the browsers in the standard of getting the information to the servers. So, this is where, and even you get the information, even after that, you have to answer a lot of questions like when did the problem happen, how many users are facing it and what's the exact file it happens and not many questions, even you start to fix that problem. So, how do we if I help is basically it's capture all the information and it collect in the someone's central dashboard. So, where you can log into that dashboard and see what's going on. So, just in the dashboard overview. So, first thing, it tells you like, if you have let's say 100 users, it can directly tell you that this problem is faced by 72 users or 10% of your user base. So, you can easily understand that this is the target, this is a small problem or this is a big problem, how it affect your business, how it affect your product usage and this is about affected users. Second thing is a very common thing like user rating distribution. You can easily see like the problems, the same problem happens on which versions of the browser, so which different kind of operating systems and so third thing is what different kind of messages you want to like, sometimes you want to catch errors and sometimes you want to catch a lot different kind of information like warnings and maybe logs for debugging our JavaScript site code. Just like server side, we don't have a standard, we're doing it for the JavaScript code. Next thing is like how the data is viewed. So, this is the, you can see like encode reference error, Google is not defined. This is an error, this happens in Chrome, 23rd version on iOS. This is just like logs you'll see in a normal server side tool. And next thing is the detailed information of like any message, like you can extend this message to the full details. The details are kind of focusing on specifying the which user is specifically getting the problem, so you can pinpoint a specific user and know that this is the user. You can see the whole history of the user that in the last two days or last month, the user has faced this many problems. And the file names and the file path, the general debugging information and the page on which page the problem happens, what was the effort of the page. You can even do modularized logging with it. If you want to, let's say you have 10 modules, you want to do this different log for different modules. You can easily kind of sort out things when you are searching for the, you are basically finding your problem in the whole bunch of thousands of logs you collected. And the geo information where the user comes from, all the geo IP related information. And a lot more about the browser of the user facing the problem, Java supporters, cookies are enabled or not, a lot many features. And apart from that what happens when you collect a lot of data, so the problem comes as like one normal day you collect 2000 and 3000 errors. So it's not human possible to get through each error log. So you have to need kind of intelligence to understand that whole collected information and give you an overview that this is the problem. You have to write this problem first. So you can see that this problem is jswivel.net caught this error. This happened to 31 times. So this can be a higher variety as compared to other things. So this is trying to give you intelligently tell you that prioritize your problem, check out this problem first rather than other problems. And so you can get some mental peace out of the project. So how to use it? It's a simple just put this code in your website and you are done. So some alternatives way of using this product is you can use a Chrome extension, you can use a WordPress plugin if you have a WordPress log. So this is some rough figure for the last month, like I don't know. So it's just 3,66,000 unique errors in stage use. So this is a use case for a company, Macosha.com. In 24 hours they captured like 5,002 errors, 753 errors affected for them out of total 1347 users. These are the distribution of the different browsers the users coming from and operating systems. So this is all I have built up to now. So I'm planning to extend this to server-side languages and give a full stack debugging kind of feature so users can, especially full stack developers can get most benefit out of it. Question and answers. I think I have time. How does it work? Can it report the stack? Yeah, like I'm currently working to, like our browsers have problems like window or on-rider doesn't provide much stack information but I'm trying to put in some features to get stack most of the time. It's not 100% but it will improve with time. What do you suggest we should do when we have a compressed minified JS? So source map is one of the thing which will evolve and I think in future we will have good solutions for that, the minified code. What is the performance effect on the user? So performance effect is as of like, if errors are not happening like the code is once loaded it's kind of a silent mode, it doesn't do anything until something breaks off or something like that. No, is it like... It's not a polling thing. It's kind of a listener. If something hit the listener then it will work. So it's working as a... Async kind of thing. So how are you thinking of the side you are talking about? So like the whole idea is like, normally we use two, three tools, one for the other side of our front-end so like under bundle all the things in one dashboard so you can easily search out everything in one dashboard and relate things also like you have one request response kind of a thing so you want to relate the front-end error with the back-end error in the whole cycle. You can easily see that this thing happens. I'm trying to do that thing. That's the idea I'm trying to work on. Is there any other context that I can get like what happens before this error? Well I think for that you have to do manual logging like you can add some information like something happens you can develop, I have to put some logic in there so that can be tracked. But automatically I don't. Not right now maybe in future. So I will say the large tools are available. Yes. Yes. So New Relic has done performance monitoring as I know. No but they have this error. I don't know how many depth it is. So there is something there. So like perform... Airbreak does the same thing. Airbreak. Airbreak. Someone bought it right? There are a few airbreak. Get it exceptional. There is Honeybatch. Are there a bunch of companies trying to like I think it's a new space and like plenty of companies I think even in I think he's also there right? So like plenty of people trying to solve the problem and problem is big enough and I think there's plenty of things can be done around it and plenty of good things can be done. So stop that. So does your thing work for Node.js? Node.js is not right now but in future it will. It's currently in browser environment as well. Thanks. One more thing please try out the program and give us feedback. Yes. Go ahead. Scientists, you will be fired by the end.