SharePoint developer’s have experienced a lot of change over the last few years. We’ve had our code run on the server code (as a full trust solution), or in a Sandbox, then on the client as an “App” (later Add-in) and now we’re coming back to Web Parts although this time they’re all client side.
I spent quite a bit of time 18 months ago creating the Collab365 Conference Platform which is built on top of SharePoint 2013 Foundation and we use Kendo UI extensively. Most of the UI is developed with MVVM and Javascript. If you’re interested – I wrote about this in depth.
I’d love to do a quick poll. If you are a SharePoint developer how do you build your SharePoint (online and on-premises) UI’s? Do you use a in-house framework or 3rd party library (like Kendo UI)?
What software stack do you use for UI?
I have used Jquery UI for custom webparts, App Parts and Jquery, Bootstrap for responsive homepages. Have also used Kendo UI mostly grids for data related requirements.Â
Hi Mark,
I am using Kendo UI in all of my last SharePoint projects.
Grid with exporting and filtering functionality is awesome.Â
I tend to stick with Bootstrap or Office UI Fabric and either ASP.NET MVC or Angular. I’ve begun throwing React into the mix just for funsies, but I mostly have used jQuery UI for components in the past.
Apart from Adobe Photoshop (what would we do without it), I use Patternry to look for existing UI patterns, Balsamiq as a wireframe, and javasctipt kit. And to ensure that the interface works perfectly on multiple platforms, I choose CrossBrowserTesting, as it allows to test every aspect of the interface. This is a basic toolset for me and other Digital Design Sharepoint developers.
