 I'm Wes Hackett, I'm the CTO at Add-In 365, Productivity and Office 365 product company in the UK. I'm also an Office Server and Services MVP for the last four years. So I first got into SharePoint in 2006 working on sort of pre-release MOS and I've been doing 2010, 2013 and then as soon as 2013 was available in Office 365, building lots of solutions, enterprises, products and stuff for Office 365 and our product company basically specialised in 365 only. So it was one of the fortunate for you that saw the framework when it was just an idea on a whiteboard nearly two years ago now and then was involved with Dev Kitchen 1 February last year so we got to see all the new ideas and framework and really have been working with the product team on and off all the way since February last year, building pre-release and then obviously when it went to public preview, helping the community, supporting the community in getting started and now it's GA, building stuff for customers. Do you know what the SharePoint framework today is? Because web parts are the first thing to arrive they really remind me of visual C-Shark web parts way back when for 2010. It's a web part container built with a particular technology that you sort of put your experience right into the middle of. So now what we've got is a React container that you can put your code into the middle of the web part and then Microsoft are taking care of bootstrapping that into the page. So it's a good first start. I think it'll be quite exciting to see where the team take that implementation, the extension points and you know beyond the web part box if you like in terms of allowing us to extend that modern UI that they've been delivering over the last 12 months. The thing that strikes me most about the SharePoint framework roadmap is the velocity. Never before have Microsoft been so open and so fast. So as a SharePoint dev that's trying to get on the train to keep up, you've got to learn new technologies, Gulp, Webpack, Yeoman Generators, all these things that kind of as a normal SharePoint developer coming from an enterprise background you're kind of not familiar with. So you know it's that velocity really and the roadmap supports kind of their view of how they're going to modernize the whole of the SharePoint UI and it's some really interesting pieces but then there's still some big chunks missing so provisioning still you know we're reliant on P&P to do provisioning and we've also got some challenges around branding. You know a lot of people still wanted to you know big RT design treatments to to SharePoint sites and there's some pretty big gaps in those areas at the moment. Favorite part of the SharePoint framework is a tricky one. I think the fact that it's moved into modern web dev stack makes it a lot more accessible. I mean we add in 365 we took decisions to take apprentices on and they've come out of university and school having done JavaScript frameworks like Angular we can take them on and get them productive against SharePoint very quickly. We haven't got to take them through a big sort of you know understanding the surface area of SharePoint before they can start building things. If I was king for the day the one thing I would add is I'd redress the balance between the amount of effort and implementation on React versus Angular. For three years the Microsoft marketing team spent a lot of effort getting us to build spas add-ins using Angular and we've kind of been left behind with the push for React. I mean I understand Microsoft want to use React and the framework is agnostic to a point but it's sometimes more problematic to use anything other than React to to do some of the extensibility. I think I would sort of look at a bit higher level and make sure that we don't over overspread the amount of customization we can do to the platform. I think there's a you know community in general is looking to replicate the development surface they had available to them from on-prem days and you know there's some questions that I've seen there's some commentary that I've seen about you know I want to extend it like this I want to do that I want to take over the UI and you know the product team themselves are saying well to make it fast to make it secure to make it future-proof we need to control a lot more of that experience you know the cloud has given you the agility and the speed and it comes with the drawback that you don't necessarily have the extensibility to the UI that you once did. So that for me is the sort of key area. Just a lack of documentation you know really good solid enterprise examples you know there's a lot of hello world there's a lot of contributions in P&P and those guys have done a great job of getting us to a baseline but we really need solid enterprise guidance you know how do we make sure we're doing all the right way how do we make sure you know because we're moving from server side to client side we need to make sure we're not exposing tokens we need to make sure we're taking advantage of the right models for security and also there's not a huge amount of information about how we can leverage the data loss prevention and the rights management EMS suite alongside our custom implementations you know because we now have to be cognizant of two factor or all of the DLP pieces when we build web parts we don't want to be leak we don't want to be the ones leaking data. I think the SharePoint framework is going to enable some of the business use cases to be solved so you know the fact we can start building web parts now that we can put on a team group site is really beneficial to a lot of enterprise organisations. The future you know Microsoft have already said they're going to talk about publishing and making you know sexy pages so we're bound to see that but I think really for me it's still limited because it's just SharePoint you know we've got Office 365 it's 17 or so services teams groups exchange you know there's no single extensibility point anymore it's you know we're just focused on SharePoint the SharePoint framework and I think you know that will that will effectively ring fence it because our company is not just looking at SharePoint as the place to put things you know teams is a really obvious one but there's there's other scenarios where you put extensibility the office clients is a great example so SharePoint framework has its place it gives us the ability to do a lot of things that we need as an enterprise and as an ISV for products but it isn't the whole story in Office 365