 Hi, I'm Clint Finley with Silicon Angle. We're here live on theCUBE, which is our streaming broadcast internet TV show. We cover all the latest and greatest in technology. Today, we're in San Francisco at the first Node Summit, which is dedicated to Node.js, which is an emerging development platform. I'm joined today by Arnaud Kazimier. He's the founder of Observit. Arnaud, can you tell us a little bit about Observit? Observit is a real-time analytics service that it's not analyzing your website, but your users. So you actually insert one line of code in your page and you can see the user's mouse everywhere on your page and see the clicks and scroll down the page and you see it reflected on your own browser. So it's just like watching over the shoulder of your user. And so would you compile a lot of statistics from this or is this just, you record a lot of the interactions? Sort of, how does the end user who's analyzing the traffic, how do they use it? We're sending all the events to our backend and then you can replay it, just like separate session or it gets aggregated as heat maps. Okay. And so you were one of the winners of Node Knockout, the most recent Node.js development competition. Which categories did you win in? We won overall, solo and utility. So you developed the original one, solo, all in your own? Yeah, solo. Okay. What's your background before starting this project? I'm originally a designer and then I moved from designing to the front end and then when Node started getting extraction, I moved to Node. So you're solving a sort of problem that you would face then as a web developer wanting to know how people are interacting with sites and applications. Yeah, how they're doing on his site and what is working and what is not working. How users are converting on a website as well. How does, how do you use Node.js in this? Our complete services runs on Node.js. We're using Socket.io for the real-time connection between the user and our server. And we're using Node.canvas to generate heat maps and we're using the queue service from LearnBoost to process all the information in real-time. Is this something that the end user has to opt into or is this something that it just, it just starts getting recorded? It just starts getting recorded. So you have to put a little privacy notes in your page that the user might be monitoring. And so this is all done in JavaScript. So there's nothing that the end user has to even download. It's just part of. There's one line of coding in your page and you're done. How old does it perform then? Does it slow the site down? It doesn't slow down the site because we're using WebSockets to send over the information. But of course we have a little performance in because you have to download one access script on your page. Well, what about on the users and does it? You won't feel any latency when you're moving around on a page. Will it increase the CPU usage or anything like that? Nope. Not a bit. Or maybe like one, two percent. It's not noticeable. Where are you going with this application now? I know you're part of the node competition here. Yeah. So are you looking for funding? Do you have funding? We're definitely looking for funding. We're currently just bootstrapping the application. And we're just hoping to build it out as a complete service. And by looking for investors, we can just push out the public release sooner. What's the business model going to look like? Will this be sort of a freemium service that people can, you know, you have an entry level tier? Yeah, we have an entry level that's like 100 recordings and then you have to pay for a monthly fee. Okay. What's on your roadmap for the development? Is there any, do you have any longer term vision for what else you want to do? Yeah, we definitely want to continue aggregating the data and getting more useful data out of it. Like where your users are dropping, so you don't have to follow one session to find out, but just an aggregated view of possible interesting sessions for you. And we want to go mobile. It's the new hot thing, so following touches and relating that as well. Okay, so I want to go back a little bit to your background, because you said you started out as a designer and then you started doing front-end development and now you're doing back-end development with Node. How hard were each of those transitions? From designing to front-end was quite easy because I just always wanted to have my designs pixel perfect. So you just have to do it yourself if you want the pixel perfect web pages. And then, yeah, Node came and I just wanted to move on, keep on learning and was just a smooth transition from front-end to back-end. It's just the same language everywhere which makes it really easy to work with. Is the whole callback model, is that hard to learn? I don't think so. It's just something to get used to, but once you know how it works and what kind of issues you're going to run into, like these funky coal stack trees with nested coalbacks everywhere, because if you just know how to avoid it, it's just simple. Were there, as you were developing, observe it, did you run into any big stumbling blocks with Node or did everything just work pretty seamlessly? The only problem that we had was with hosting that are not all supporting WebSockets. So that's something we were bumping against because the WebSocket spec kept changing and changing and not every hosting company can keep updating their stack to support the current WebSockets. Right, and not all browsers. Well, all the major browsers supporting WebSockets now, I know Mozilla took it out for a while but they put it back in. Opera is supporting it now. Opera is supporting it, Chrome, Safari. Has the development of it stabilized then of the spec? The spec is finalized, so that's great news. But there are always some issues with cross-bousers support, even with WebSockets. They're bugs everywhere. So you just gotta be aware of those issues. So that seems more like it's more of a front-end issue rather than a Node.js issue. It's not a front-end issue. Yeah, but you also make sure that your back-end of Node is up-to-date with the different WebSocket protocols. Of course, we've got really old versions of Safari. It's using like Draft75 and the newer one using the latest WebSocket specifications and you want to support them all to have a great browser support range. Okay, well, that's all the questions I have. Is there anything else you wanted to let our viewers know about? No, they can sign up for a beta on beta.observe.it. And we're rolling out beta next week, slowly. Great, well, good luck with the beta. Yeah, thanks. We're gonna take a break.