 Hey, welcome back, everybody. Jeff Frick here with theCUBE. We're at Node Summit 2017 in downtown San Francisco, about 800 people, developers talking about Node, Node.js, and really the crazy adoption of Node as a development platform, enterprise adoption, everything's up into the right, some crazy good stories. And we're excited to have somebody come and write off his keynote. It's James Bellinger, he is an engineer at Twitter. James, welcome. Thank you, thank you for having me. Yeah, absolutely. So you just got off stage and you were talking all about Twitter Lite. What is Twitter Lite? I like Twitter as it is. Well, so Twitter Lite is a optimized, it's a mobile web app. So if you pull up your phone, open up the web browser and go to twitter.com in your smartphone web browser, you get a Twitter experience that we're calling Twitter Lite. Okay. And it used to be a little bit out of date, but we've been able to update it using a lot of new, exciting web technologies. And so now we have this thing that feels very much like a native web app. They call them progressive web apps these days. And so we're using that as sort of a way to sort of compete in areas and markets where maybe native apps are less able to compete, where people don't want to download a 200 megabyte iOS app. They want something that fits under 600 kilobytes. Okay, so you had the Twitter Lite app before and then this was really a redeployment or are we getting it wrong? Well, we had a web app at mobile.twitter.com and it was just sort of the mobile web app. Okay. But we sort of really rewrote everything and that includes the backend on Node and then we're now sort of pushing that and calling it Twitter Lite. Okay, and when did that go live? Three months ago. Three months ago, okay, super. So obviously you're here at Node, you just spoke it in Node. How was the experience using Node tool set versus whatever you had it built on before? It's definitely faster in every way. Faster in every way, that's a good thing. Let me catch that. Be more specific. There's those benchmarking people. We need them back over here. It is very fast for how we apply it. It's really fast for development speed and perhaps the biggest win is that on both sort of areas of our stack, whether it's the part of the application that runs on the browser or it's the part of the application that runs inside the Twitter data center, we have one language and technology. So when a problem comes up and an engineer needs to go and find the problem and fix it, they don't need to sort of, oh, well, that's server code. I don't know how it works. And it's written in this language I don't understand. We really just have one application and it happens to run in both places. And so it really improves engineering efficiency. And you saw that in the development process, QA and the ongoing, yeah. And it was a more, so it's more like the guys that were more front end that now have access to the back and then the other way around, is that correct? Yeah, it's a little bit of both. You know, I think before, I think there's people that they really like Scala and they only want to work in Scala or there's people that really don't like it. So you end up, I think, having engineers kind of get balkanized by their technology choices and their kind of preferred systems. But I think it really sort of tears down a couple of walls. And so it improves engineering efficiency that way, but we found also that some of the tool sets and the tool chains that we're using allow engineers to just sort of move faster. Right. So whether that's like recompiling the service in like one second instead of having to wait for multiple minutes, there's just sort of less time spent waiting. Right. And in terms of don't share anything, you're not supposed to share, but in terms of frequency of releases and kind of ongoing maintenance and kind of the development of the, I won't say the app, not the app. I guess it is the app. Going forward, how has that been impacted by moving this platform? I think it might be too early to say. We've, right now, we've got about 12 to 15 engineers and we're ramping up. And I think it might, we're kind of looking to finish around 25 engineers by the end of the year. So the sort of team and contributor base of the kind of like core team that are working in the app is growing. But otherwise, we're releasing every day, we're kind of always pushing code, we're running experiments a lot. I don't know if that answers your question. So it sounds like it's a little easier, but you're still doing everything you were doing before, but now it just feels like it's easier. Well, talk to me in a couple of months and maybe I'll have some better answers for you. So the other thing, if I talk to you in a couple of months, I talk to you from a year from now, just in terms of, as you look down the road, what this opens up, what are some of your priorities now that you've got it out? You said you've been out there for three months. What's kind of next on your roadmap, your horizon? So far, I think we've been really encouraged by the success of using this stack for development. So we're looking to kind of double down on that. So that means looking at some of the other Twitter web apps, or sorry, Twitter apps in general, the other ways that people use Twitter and to sort of look at how they were built and to see because we're using React and because we're using, I think, technologies that make it very easy to be responsive and either you have a wide layout or a very narrow layout or work offline, we have a lot of potential to sort of cannibalize or replace and also update some of the existing apps that maybe don't get the attention that they need. So there's some of that. And then I think Twitter Lite as a product, I think that we're going, we're looking to really expand its reach and make a big push in some of the developing areas. Yeah, because the other thing people don't know, I mean, Twitter's acquired a bunch of companies over the years. So we've heard some examples earlier today where that's a use case when you do have the opportunity to maybe redo an acquired application, that those are kind of natural opportunities to look to redo them with this method. Yeah, for sure. Yeah. All right, cool. Well, James, thanks for taking a few minutes. Thank you. Congratulations on the talk. And I'll thank you for you next time I go to Twitter Lite. Okay, yeah, thank you so much. All righty. He's James Bellinger from Twitter, I'm Jeff Rick. You're watching theCUBE from Node Summit 2017. Thanks for watching.