Session on development of SharePoint-powered apps for mobile and tablet devices - ShareConf, Dusseldorf/Germany, June 2012

3. The problem
Current situation
SharePoint data in the enterprise
SharePoint data in the world

4. Good
Old Times

6. consume data?
One System, one hardware, one OS Windows Everywhere
Homogenous IT environment Microsoft market leader in operating systems, server and
productivity software

8. today?
• The way how we are consuming information
has inevitably changed
Different hardware, multiple OSs Strangers in the night
Heterogonous IT environments Incompatible systems, incompatible identities, one data

9. • The
• Most relevant corporate data stored in
SharePoint or leveraged through it

10. challenge
Keep it SharePoint style Keep it device-conform
Data and permissions managed in SharePoint Visualization of the data looks different on different devices

11. response

12. approach

13. on mobile devices
• Way too much document centric
• Devices are not ideal medium for
collaboration and document editing
• Employees want information, not pure documents
Devices are… BI, Search, Solutions…
...meant to consume information. Great deal of SharePoint power is left out in mobile apps

14. solution
SharePoint apps are… Custom apps are…
...like SharePoint out of the box features …like customizations and custom solutions we were always
developing with SharePoint

15. today?
Client-Server architecture Mimicking the business layer in UI Impersonation what?
We stopped using that decades ago …and producing some very ugly Doors Open Days 24/7/365
JavaScript code on the way

16. apps

17. entapps
• The device needs to be in the domain
Know your rights Comparable with SharePoint solutions
Users can not do more or less SharePoint solutions for mobile
than in SharePoint interface itself and devices

18. Surface
• …loved by the admins

19. scenario

20. CONFERENCE ORGANIZATION SHAREPOINT SITE

21. architecture outline
Use architecture patterns Windows RT Metro
Layered, modular architecture, with Windows RT App will be consuming
full separation of concerns the WCF service

22. architecture outline

23. ENTAPP WITH WINDOWS RT (METRO STYLE) APP

24. reaching out
• Variety of devices
• Variety of operation systems
• Native vs. HTML5/jQuery
Native Apps HTML5 / jQuery apps
Are usually more user friendly, more in style of specific Are cross-device compatible, can be published as apps in
device, can use full power of the device, and usually faster most app stores, easier to maintain in the future
to develop

25. Windows 8 iPad/iPhone HTML5/jQuery
Windows Phone Android Blackberry

26. problems

27. rest services
• You can specify the endpoint yourself
REST Services It’s WCF after all
Need to be hosted inside the SharePoint Web Rest services in SharePoint are implemented through
Application, otherwise the authentication mechanisms Windows Communication Foundation
will not work.

28. wcf services
• http://server/_vti_bin/Service.svc/negotiate
• http://server/_vti_bin/Service.svc/ntlm
• http://server/_vti_bin/Service.svc/anonymous

29. wcf services
• But you can
HTTP Module

30. architecture outline – Windows Phone 7

31. architecture outline – HTML5 and jQuery

32. APPS WITH WINDOWS PHONE AND HTML5/JQUERY

33. http://sharedove.azurewebsites.net/

34. 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 tokens
Azure Control Services REST + ACS
Can be used to act as identity provider for SharePoint. When using Claims with REST services, they expect SWT
SharePoint expects SAML 1.1 tokens tokens, so ACS needs to be configured to return it.

35. recapitulation

36. questions?
Adis Jugo
Technology Advisor
T +49 89 3186 7154
M +49 151 52 602 822
F
Mail:
+49 7361 55 621 20
adis.jugo@plan-b-gmbh.com
@adisjugo
Blog: www.adisjugo.com sharedove.codeplex.com