consume data?One System, one hardware, one OS Windows EverywhereHomogenous IT environment Microsoft market leader in operating systems, server and productivity software
today?• The way how we are consuming information has inevitably changedDifferent hardware, multiple OSs Strangers in the nightHeterogonous IT environments Incompatible systems, incompatible identities, one data
• The• Most relevant corporate data stored in SharePoint or leveraged through it
challengeKeep it SharePoint style Keep it device-conformData and permissions managed in SharePoint Visualization of the data looks different on different devices
on mobile devices• Way too much document centric• Devices are not ideal medium for collaboration and document editing• Employees want information, not pure documentsDevices are… BI, Search, Solutions…...meant to consume information. Great deal of SharePoint power is left out in mobile apps
solutionSharePoint apps are… Custom apps are…...like SharePoint out of the box features …like customizations and custom solutions we were always developing with SharePoint
entapps• The device needs to be in the domainKnow your rights Comparable with SharePoint solutionsUsers can not do more or less SharePoint solutions for mobilethan in SharePoint interface itself and devices
reaching out• Variety of devices• Variety of operation systems• Native vs. HTML5/jQueryNative Apps HTML5 / jQuery appsAre usually more user friendly, more in style of specific Are cross-device compatible, can be published as apps indevice, can use full power of the device, and usually faster most app stores, easier to maintain in the futureto develop
Windows 8 iPad/iPhone HTML5/jQueryWindows Phone Android Blackberry
rest services• You can specify the endpoint yourselfREST Services It’s WCF after allNeed to be hosted inside the SharePoint Web Rest services in SharePoint are implemented throughApplication, otherwise the authentication mechanisms Windows Communication Foundationwill not work.
considerations • Possible • Sending username and password • Storing username and password• Using Claims and federated identity providers • SharePoint + ACS => ACS must return SAML 1.1 tokens • Securing REST with ACS => SWT tokensAzure Control Services REST + ACSCan be used to act as identity provider for SharePoint. When using Claims with REST services, they expect SWTSharePoint expects SAML 1.1 tokens tokens, so ACS needs to be configured to return it.