 Hi, my name is Corey Roth and I'm an independent consultant, specializing in Office 365 and mobile. As a SharePoint developer, I got my background started around 2007 when I got thrown into a project on my first kind of consulting gig. And I said, hey, you know SharePoint. At least pretend you do. You're going to the client next week. I said, great. And my first kind of project was centered around SharePoint Search. And so I started contributing in that area and started speaking about it. And then, you know, kind of wrote in good tales for that as I, you know, then later transitioned into Office 365 development. And, you know, people keep asking me about search and it's not something that, you know, people focus on as much anymore. I would say with the SharePoint framework I started, you know, before I went to GA. And I, you know, I'm dabbling at it is really the extent of it, honestly. I haven't done any real projects on it, but I've been looking at it quite a bit to see how it, you know, will fit my client's needs. You know, I like the direction that's going. I've been doing a lot of mobile development, so I have a background there. And they leveraged a lot of principles that platforms like Cordova use with the bases on DoJS, the use of TypeScript. And so for me, that wasn't quite the, you know, culture shock that other people experienced coming over from it. And I see a lot of how those paradigms came over. And so I think they're going in the right direction. I think it's got, you know, a lot of maturing to do. But it just did GA and there's a lot of things coming. And I'm excited about what's going into Pipeline. I think it's a good starting point. I think, you know, it's, I'd like to see some pieces kind of come to it. We'll talk about that. But, you know, I think if you want to build a web par, it's, you know, it's connected. It's built on, you know, tool chains that are established for other communities. And so I think it will work well. It's just a matter of finally getting, you know, the last bits and pieces that we need to do, you know, more of the advanced types of customizations that we traditionally did with, you know, the add-in model and as well as, you know, traditional server-side code development. I think the roadmap has most of the things we care about on it. I think, you know, we have web parts now. We're going to start getting things where we do more granular customizations on pages and as well as the whole page itself. And so I think when those are all in play, I think you'll be able to do some great customizations at SharePoint using this new model. This shift to DoJS and TypeScript, you know, I know that's a challenge for some people, but I think it's a great way to do it. You know, it's what I'm familiar with now and, you know, I've come to love it. So I think it provides you, you know, a good environment. It's decoupled from the server and, you know, you can run it wherever and it gives you a lot of options, of course. You don't necessarily have to follow one framework or the other, although it's certainly easier with some, as we know. But I think it's a great way to do it. When it comes to changing, I would like to see a little less dependency on React. I think, you know, it is a good choice for it and I understand it. But I think it's also a big shift for a lot of people and I know other people have other preferences of frameworks and not that you have to use React. But I think, you know, if we had a little more options and we weren't quite so locked into it, you know, you could argue with you or not. But I think I would like to see other options, including Angular and, you know, whatever flavor of, you know, View or JavaScript library that you'd like to use be supported. And I guess they're all supported, right? But, you know, we'll see a little more love. I think the challenge is going to be adoption from legacy SharePoint developers, honestly. I think, you know, as a SharePoint developer, we, you know, we pretty much missed the world of the VC and the ASP.NET stack, you know. We were locked into what SharePoint provided us. We were always a version of the .NET framework behind things like that. So, as a result, a lot of SharePoint developers didn't have to learn some of the newer stuff and when they had to, it's, you know, okay, whoa, this is totally a shock to them. And so, the switch to Node.js, different tooling, that's just different. And it's not the structured C-Sharp do whatever I want to on the server, you know, type mentality. So, I think it, although a lot of other developers, you know, are already using this for, you know, single-page applications and things like that. The SharePoint world, I think a lot of that passed them by and they're having to play catch-up. So, I think that will be the biggest challenge at least is, you know, burning those tills and playing catch-up a little bit. As far as roadmap where I hope to see the SharePoint framework, I would hope to see a more mature generator. So, you know, as I mentioned, we can generate, you know, different types of parts. I'd like to see more things that we could do. Right now, we're kind of limited to web parts. We know we have some things on roadmap, but, you know, I would like to see full control of the page. I'd like to see we'll do anything to a list of document library, you know, injecting things, you know. Any of those kind of customizations that we used to do with the traditional server-side models. And so, I think, you know, we'll see some of that probably come out to play here in the next, you know, six months to a year. And I think, you know, on the adoption side, hopefully we'll start seeing an uptick of that as well, although I think it'll be a little slow going at first. But we'll attract new developers too, so that's kind of an interesting aspect as well.