Home » sharepoint » SharePoint 2013 » JavaScript Plays an Important Role in the SharePoint 2013 App Development Model

JavaScript Plays an Important Role in the SharePoint 2013 App Development Model

With SharePoint Server 2013, Microsoft® has isolated the server from some of the possibility of unintended impairments to server performance by limiting custom systems development options to client-side processes, only. This “App” development model, as Yaroslav Pentsarskyy presents in a video tutorial series titled SP13-303 SharePoint 2013: Development Video Training Package is built around the universal client, meaning the web browser. So JavaScript is an excellent programming language for the SharePoint 2013 App Development model.

I wrote several posts to this blog on the topics included in Yaroslav’s tutorial set. I’m revisiting the topic with this post to illustrate how organizations with a serious commitment to SharePoint 2013 may want to include an active App development effort as a powerful feature driving end user adoption for the SharePoint 2013 computing platform.

Custom applications make sense as a means of empowering groups within an organization with automated methods of achieving their own business objectives. The cost of developing systems with JavaScript (and even the jQuery library of functions) should be affordable for most organizations. Since the same tools are also useful for branding SharePoint sites (JavaScript, CSS, jQuery), it makes sense to include the same personnel in the App Development effort.

The browser serves not only as the universal client for desktop computing, but also for tablets and even smart phones. So once a system conforming to the SharePoint 2013 App Model has been created, the additional effort required to expose the system for consumption by tablet users, or mobile workers via smart phones is relatively insignificant.

The plus side of all of this effort, from the perspective of SharePoint adoption, is to increase the “stickiness” of SharePoint 2013. Once computing systems can be implemented in the office, or on the road, or even at a home office, personnel will be more likely to embrace new computing methods for SharePoint 2013. Once they start to consume the new processes, they will be far less likely to abandon them.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved

Comments are closed.