During the month of December, 2014, Microsoft published over 5 hours of video training content on the SharePoint App Model. This training has been packaged into 6 segments, each approximately 50 minutes in length. Each segment is led by two senior program managers who each bring extensive experience with SharePoint to the task: Steve Walker and Vesa Juvonen.
I have already written a post to this blog on the second segment in this set. The title of my post is Microsoft recommends branding SharePoint Online, Office 365 with themes, alternate CSS and other CSOM methods rather than creating custom master pages.
I should also note some conversations I have had with developers who have expressed some frustration with the SharePoint App Model. But, regardless, at least in theory, the App Model makes sense. One would hope, over time, the issues developers have raised with it are worked out to everyone’s satisfaction.
The two primary reasons for proceeding with an App model for the on-premises SharePoint computing component, for customization purposes, appear to me to be:
- safeguarding inheritance. This amounts to preserving components, like Master Pages, in out-of-the-box condition, so updates can proceed without a hiccup
- and security. When custom processing occurs on the client-side, IN THEORY, the server is insulated from malicious activities, viruses, malware, etc
By following the methods presumably communicated in the other 5 segments of this extensive video training course, pressing needs for customizations (to name simply one of these, just consider the likely extent of organizational appetite for branding SharePoint computing UX for mobile devices) can be met with approaches more likely not to impair server performance, than anything else. So I look forward to reviewing the other segments of this set and publishing opinions on points likely to be of general interest.
©2015, Ira Michael Blonder & Rehmani Consulting, Inc. All Rights Reserved