SharePoint 2013 provides an exhaustive list of options in terms of API set, when it comes to application development. The SharePoint 2013 platform provides the following options for developing applications around SharePoint.
- Developing an app for SharePoint
- Developing a Custom Web Part for a SharePoint Page
- ASP.NET application rendered through IFrame on a SharePoint Page
- Javascript/EcmaScript running in a Site Page
- Silverlight application(hosted in a website or running in a mobile device) accessing SharePoint data
- .NET Client application accessing SharePoint data
- Windows Powershell
- Timer job running on a SharePoint Server
The developers need not acquire any new skills for developing applications on SharePoint 2013. The developers can continue to leverage their existing skills on JavaScript, ASP.NET, Windows Powershell, Silverlight, Windows Phone, .NET Framework and REST/OData. The following table provides an overview of various development scenarios around SharePoint 2013 and the relevant object model to be used for each scenarios for development.
| No | Development Scenario | Object Model |
| 1 | Development of custom web parts | Server Object Model |
| 2 | Develop of custom application page | Server Object Model |
| 3 | Development of User Control | Server Object Model |
| 4 | Development of Custom Workflow | Server Object Model |
| 5 | Development of Custom Timer Job | Server Object Model |
| 6 | Development of Custom Event Handlers | Server Object Model |
| 7 | Development of Windows Phone App to perform CRUD operations on SharePoint data | Mobile Client Object Model |
| 8 | Development of Windows Phone App to implement Microsoft Push Notification Service that alerts mobile device (for events in SharePoint) | Mobile Client Object Model |
| 9 | Development o f LAMP (Linux-Apache-MySql-Php) application that performs CRUD operations on SharePoint data | REST / oData end points |
| 10 | Development of iOS or Android application that performs CRUD operation on SharePoint data | REST / oData end points |
| 11 | Development of ASP.NET application that performs CRUD operations on SharePoint data outside of firewall | JavaScript client object model |
| 12 | Development of an HTML / JavaScript applications that performs CRUD operations on SharePoint data | JavaScript client object model |
| 13 | Development of ASP.NET application that performs CRUD operations on SharePoint data inside firewall | .NET Framework client object model or Silverlight Client Object Model or REST / oData endpoints |
| 14 | Development of a .NET client application that performs CRUD operations on SharePoint data | .NET Framework client object model |
I’d explore more on SharePoint 2013 and keep sharing my leanings in the forthcoming posts.
Musings on Cloud, Containers, Serverless and DevOps 
Pingback: SharePoint 2013 various object model overview - My experiments with SharePoint, Azure and .NET using Visual Studio