SharePoint Apps and the Architecture of the new Cloud App Model Introducing Cloud App Model Designing Apps SharePoint-hosted Apps Key Learnings

Introduction to SharePoint Apps and the new Cloud App Model. Learn how to create and deploy SharePoint Apps to Office 365. Get introduced to new development client-based models and learn how to build modern responsive apps for SharePoint Objectives: Introduction to SharePoint Apps Learn how to build your first SharePoint App for Office 365

Why do customers want to customize? Why do customers want to upgrade? What’s the number one cost driver in projects? What’s the number one reason for support cases? What’s the number one issue blocking upgrade?

2003 – What is an Application? SharePoint was not an Application Platform, except web parts Investments were in portals and content 2007 – Everything is an Application! Push to embrace SharePoint for LOB applications Experience was to write custom server side code 2010 – Choose the right Application SharePoint and Developer Tools come together Silverlight, CSOM and other new capabilities Partially trusted code reduces impact and risk to farm 2013 – Redefine Application as App… Client side experience via html or iFrame Leverage CSOM and REST APIs from Azure and other clients Investments in app discovery and management via SharePoint store

Custom Code on server Root cause of most SharePoint outages and issues Lots to deploy Requires a big server touch Not possible in hosted environments Sandbox Solutions Possible in hosted environment Limited set of things you can do In both, developers must know SharePoint API

Introducing Cloud App Model

New apps A new class of apps enabling new scenarios and user experiences. Familiar toolsets Embracing web standards to provide developers with choice and flexibility. Flexible lifecycle Deploy and maintain your apps publically or internally with flexibility and control.

Deployment Options On-Premise Farm Installation Hosted Installation Development Options Farm-Trust Solution SharePoint-Hosted App Cloud-Hosted App Development Tools Web Browser SharePoint Designer Visual Studio Eclipse, LAMP, Etc.

Public Marketplace Similar Windows Phone Marketplace Subject to submission process & approval Admin approval possible Corporate Catalog Apps developed internally Apps acquired and approved for internal use Custom Deployment Process Developers can use remote / local SharePoint & Windows Azure APIs to deploy apps with custom code These APIs are restricted to the developer site for tooling scenarios

New SharePoint App Model is the preferred route for building app scenarios Provides most flexibility in development technologies, capabilities & infrastructure choices Provides highest level of process, user & data isolation Both full-trust & sandbox solutions ideal for deep customizations to SharePoint, for example: Provisioning custom master pages, page layouts, branding assets Deploying advanced administration scenarios, like timer jobs

Demo Everything is an App

Designing Apps

ShapeDescriptionExample Immersive App (Full Page) App that implements a new scenario for customers Resource Tracking, Budgeting App PartProvides new parts you can add to your sites Weather, Team Mascot, News Extension App (Custom Action) Add new actions for documents and items Display Document Visualization, Print to Print Service Vendor

App Web Parent Web SharePoint-Hosted App Provision an isolated sub web on a parent web Reuse web elements (lists, files, out-of-box web parts) No server code allowed; use client JavaScript for logic, UX Provider-Hosted App “Bring your own server hosting infrastructure” SharePoint Web Get remote events from SharePoint Use CSOM/REST + OAuth to work with SP Cloud-based Apps Your Hosted Site Autohosted App Windows Azure + SQL Azure provisioned invisibly as apps are installed Azure SharePoint Web

JavaScript Library Silverlight Library.Net CLR Library Custom Client Code Client Server _api is new alias for _vti_bin/client.svc REST OData JSON CSOM

SharePoint-hosted Apps

Sub web of site collection (SharePoint-hosted) “One app – one Web (SPWeb)” Apps can deploy only web scoped features Can include app parts or ribbon and ECB custom actions Site collection resources deployed using classic solution options End users cannot manipulate app web to avoid breaking of the apps using browser or SharePoint Designer

Host Web App Web Lists / Libraries Declarative Pages CSS Files JavaScript Files Custom Actions for app Client Web Parts

APP1UID Unique ID given to each app installation in tenancy Makes each app domain unique GUIDAPP1 Name of SPWeb under where app is installed Developers have control

Office Developer Tools for Visual Studio 2012 Default.aspx Main page of the app Web Part Page Script and Style references Elements.xml Installs home page to the isolated app site SCRIPTS App.js Template script file Elements.xml Installs script file to isolated app site APP MANIFEST AppManifest.xml ProductID, Version, Title Tile and StartPage Urls AppEvent Urls: Installed, Uninstalling, Upgraded App Permission requests

Demo Building your first App

Key Learnings

It is V1 (but quickly maturing)

For on-premise installations no single App Catalog for multiple web applications and farms No auto-activate for apps Not all artefacts can be included in apps (like web templates)

Backup/restore Protecting against data loss (the app is uninstalled)

No way to secure against malicious apps in Office store We can add Admin reviews, but no guarantee

Current version of Apps not really suited for anonymous Internet Scenarios

Apps do not work with several zones (e.g. AAM). All requests are served out of default zone (eg. authenticated zone for authors and anon zone for public users)

Start doing Evaluate Apps as preferred option Use CSOM or REST Leverage JavaScript frameworks, like Knockout Host business logic outside SharePoint Use remote provisioning Stop doing Server OM C# Code! New Full Trust Code solutions Sandboxed solutions

Evaluation Create a Text message on your phone and send it to 1919 with the content: PR I liked it a lot Session Code Morten Performance (1 to 5) Match of technical Level (1 to 5) Relevance (1 to 5) Comments (optional) Evaluation Scale: 1 = Very bad 2 = Bad 3 = Relevant 4 = Good 5 = Very Good! Questions: Speaker Performance Relevance according to your work Match of technical level according to published level Comments Henrik Performance (1 to 5)

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.