by Friski Yudhi Pratama, Analyst Programmer at Mitrais
Should you move to SharePoint Framework?
This technology does not replace other development models. Developers still can choose which development method is best for their requirement. A few things to know about SPFx are:
The code will run based on current user privileges. If a user has permission to edit a list, then SPFx code can execute that list too. Therefore, there is no elevating privilege feature as we found in full trust farm solution. This promises better security and maintains the integrity of the server.
Microsoft announced that SPFx can be used in SharePoint Online immediately, will announce support for on-premise servers shortly, so that all server types will be supported.
SharePoint Framework is targeting for a more modern SharePoint UX. It is improving the site so users can access it from any device type.
SPFx supports open source tooling such as project scaffolding Yeoman, build-test script with Gulp, import other js libraries with npm, and many more. Using this framework, we can separate development front-end and back-end. Designers can focus on creating UI components and back-end developers can create APIs as Add-On solutions to be consumed by the SharePoint framework model. This approach improves working speed and avoids dependent development.
In the end, it is your call which development model to use. But, as a developer you need to be aware that this framework could be the future of SharePoint development. Knowing how to use it, and its pros and cons can support developer decisions how to plan their SharePoint development projects.