 My name is Prashanta Ji Bhoyar. I'm from Washington DC area and currently working as senior consultant with Witham Smith & Brown. So I started working on SharePoint back in 2009 and since then I have worked on like all version of SharePoints that are out there. And I see myself as a jack of all trades. So I have done pretty much everything except branding. So my first interaction with SharePoint framework happened in Microsoft Developer Kitchen back in February 2016. That was the first time they showed the early bits and they let us play with that. In return we had to provide them feedback. So that was the first time I got introduced with it. So as of today I will say it's definitely a right step in right direction and the way or the strategy or the vision Microsoft have is really good. Because that's where all other industries or all other developer ecosystem are going where they are using more and more open source tools. So you're not tied off with let's say enterprise specific tools like Visual Studio. That's really good. So I went to the roadmap on their site and so far it looks good. So they're talking about introducing better ALM story. They're also talking about supporting the single page app in your future. They're also talking about introducing the SharePoint framework to SharePoint on-prem. Which is I think one of the biggest feature or step will be. The local development, that's my favorite part because now with SharePoint framework I can pretty much do development on any machine. And also I don't need access to the internet. So I'm no longer tied off with you know you need a specific machine which needs to have like specific RAM or specific servers running. That's not the case. That's my favorite part about it. So one thing I will add is the ability to develop web parts for a specific site. Because the real competitor for SharePoint framework as of today in SharePoint online is the various methods people use. Writing content editors and script editor web part just to get things that you wanted. And a lot of organizations they have like some kind of silos and they don't have always access to the tenant admins. So to do deploy any web part if I had to work with tenant admins all the time it may not work for a bigger organization. So people would have like some kind of flexibility where okay this is your site collection. You can play with it. You can do whatever you want and you can build your own solutions for it. The one thing I will change is the messaging that's happening from Microsoft. Because what I personally seeing is Microsoft is doing a really great job in promoting power apps and flow especially Office 365 team. They are going to a lot of events. They are like arranging a lot of Twitter jams. They are also like arranging a lot of sessions. But same is not true for SharePoint framework. Like you hear from Microsoft about SharePoint framework in build confidence or in ignite. There is always patterns and practices call is there but the real face time with SharePoint product group is missing. So from developer point of view I think the biggest challenge is especially if you are doing server side development from long time. Getting used to the tool chain because there are a lot of terms that you may never have heard of. And you may like feel a little bit frightened like oh what's this? Now just to write a single web part now I had to learn all these six or seven things and I had to like go through this setup. So that is the biggest challenge I think from developer point of view. And from the organization's point of view is so one way Microsoft is announcing okay Office 365 is a software as a service. So you use it and you shouldn't be like customizing too many things in SharePoint and this is a framework to write custom things. So there is a lot of uncertainty or people are like kind of playing what weight and watch game just to see how this framework gets matured. And whether we should really invest in time and deploy the solution using that. And recent announcement from Microsoft on couple of other development models also did not help. Like they announce about access services, they announce about sandbox solutions. So some people some organizations a little bit they're playing weight and watch game right now since it's a fairly new. And I personally think definitely there will be a single page application support because right now if you have a web framework where you just have can create web parts. A lot of people may not use that right away because there is alternate method available which a lot of people are using especially developers from last three years ever since. They are starting moving to Office 365 and they announced the add in model and add in model there are some restrictions like you don't have the full control on the page. Whereas using some other methods like injecting script editor web parts or content editor web parts you can pretty much do a lot of things using the Microsoft REST APIs. So if that story is good and it's there and it's readily available whereas here okay I can do this web part but I can use this framework but I can only build a web part for rest of the stuff I had to use something else. So for developers my advice is go through the Microsoft documentation on SharePoint framework. It's one of the best written documentation because not only Microsoft folks are writing it some of the folks from community are also helping to make it updated. So if you go through it develop your first hello world like web part don't just get like to walk down by okay I need to learn all this stuff. There are a lot of uncertainty like people think okay just to write a simple web part I had to learn TypeScript I had to learn let's say React or I had to learn Angular that's not true. Like you can use any framework of your choice or you can simply go with JavaScript or jQuery as well. So just go with that flow and see how's the experience is and once you go with that like you know it's like riding your first bicycle or riding your first bike. Once you do that once you feel it okay now I can do it and you can then start implementing or developing some additional or more complex web part. So the biggest challenge I think when it comes to adoption of SharePoint in developers is the landscape is changing so much in Office 65. Like Microsoft is doing really good job of announcing new products like a team then there is a group there is a flow there is a power apps. So what's happening is to do like implement customization I have to now fight a war on five different fronts. Not only I had to learn SharePoint framework I had to learn what's happening with teams I had to learn what's happening with power apps I had to learn what's happening with flow. I had to learn what's happening with Azure functions as well you know and with increasing adoption of Office 65 more and more organization are spending less and less money in customization. And what they are expecting especially this is true in Washington DC area is you don't have a lot of people to you know right customization for SharePoint or Office 65. You have a couple of people and then if you are in the same board then you have that means you have to keep track of everything that's happening latest and greatest. And somehow I feel since SharePoint framework is only for web parts a lot of time it doesn't get the focus or attention that it should get from the developers.