@jerry_yasir
2007
IIS
SharePoint
Code runs from GAC on
same w3wp.exe as
SharePoint web application
2010
IIS
Sand
box
SharePoint
Code runs on
SPUCWorkerProcess.exe
or calls client.svc (CSOM)
2013
IIS with _api
App
SharePoint
Code runs outside of SharePoint
but has trust to leverage
capabilities exposed in _api
Build a new class of apps that extend and personalize the way we create
and consume information right from within Office and SharePoint
New Apps
A new class of apps enabling new
scenarios and new user experiences
Familiar Toolsets
Embracing Web standards to provide
developers choice and flexibility
Flexible Lifecycle
Deploy and maintain your apps publically
on the new Office Store, or internally with
Flexibility and control
Cloud-based Apps
Get remote events from
SharePoint
Use CSOM/REST +
OAuth to work with SP
Provider-Hosted App
SharePoint
Host Web
“Bring your own server hosting
infrastructure and technology platform”
App Web*
Autohosted App
Windows Azure + SQL Azure provisioned
invisibly as apps are installed
SharePoint-Hosted App
Provision an isolated sub web on a parent web (separate domain)
• Reuse web elements
(lists, files, out-of-box web parts)
• No server code allowed; use client JavaScript for logic, UX
Your
Hosted Site
(separate SharePoint
domain)
SharePoint
Host Web
App Web*
(separate SharePoint
domain)
SharePoint
Host Web
App Web
(separate SharePoint
domain)
Azure
A SharePoint Hosted App
Tenant A
.app
App Developer
.app
App Catalog
Site Owner
Tenant Admin
.app
Site Owner
Tenant B
Site Owner
SharePoint Store
(Office Marketplace)
Site Owner
An Auto-Hosted App
A Basic Provider Hosted App
SharePoint 2013 App Catalog