Reach your audience with a share point mobile app

  • Published on

  • View

  • Download

Embed Size (px)


This webinar covers some different approaches to mobile solutions and includes a case study of SchoolLink, a SharePoint mobile app Habanero designed for the Surrey School District. A custom SharePoint web service allows content published on the districts website to be pushed out to different mobile devices, increasing the communication between administrators and parents and managed by district staff through their SharePoint portal. The app was developed using the PhoneGap open-source framework which allows for easier development across different device platforms. Hosted by Customer and Member Portals Practice Lead Mallory O'Connor, the one-hour session will also provide helpful insights on content, app maintenance, and technology that may help participants with a current project, as well as offer a chance to learn about the ways content can be extended from a SharePoint portal to mobile devices.


  • 1.Reach your audience with a SharePoint mobile app May 22, 2013

2. Hello brian edwardsDirector, Portal Offeringsmallory oconnorPractice Lead, Customer and Member Portalsmark biceSolution Architect, Front End 3. About Habanero 4. We are passionate about helping people and organizations thrive. 5. Employee PortalsCustomer PortalsMember PortalsConnecting parents to their childrens schools. 6. About the Habinar 7. #habinar 8. Reach your audience with a SharePoint mobile app 9. Goals for todayreview approachescase studythings to considerfor mobile experiencesSchoolLinkinsights 10. Lets refresh on approaches to mobile experiences 11. Selecting a mobile approachAnticipated user scenariosBusiness objectivesNature of content / functionalityDevelopment / sustainment capacityDelivery timelinesAvailable budget 12. Mobile decision tree Mobile RequirementsMobile WebDedicated Mobile SiteMobile AppResponsive SiteNative AppHybrid AppPhoneGapiOSAndroidWindowsiOS 5, iOS 6Gingerbread, Ice Cream SandwichWP7, WP8OS 5.x , OS 6.0+Smart Phone DevicesTablet Devices- iPhone - Android smartphone - Windows smartphone - Blackberry smartphone- iPad& iPad Mini - Android Tablet - Microsoft SurfaceHybrid Devices - Galaxy NoteBlackberryTitanium 13. mobile web vs. mobile app Mobile experiences consumed via a local device browserMobile experiences consumed via specific app downloaded from an OS marketplace(i.e. Safari)(i.e. App Store, Google Play, SharePoint Store) 14. Mobile development approaches 1. Dedicated mobile site 2. Responsive siteMobile Web3. Native app 4. SharePoint 2013 native app 5. Hybrid framework appMobile App 15. Dedicated mobile site 16. Responsive site DesktopTabletPhone 17. Native apps 18. SharePoint 2013 native apps 19. Hybrid framework app Wrap your app with an open source frameworkDeploy to multiple OS platforms 20. Case study: SchoolLink 21. A little background: Surrey School District 22. Vancouver 23. VancouverSurrey 24. 70,000 Primary, secondary and adult education students 25. 130 + Schools, learning centres and programs 26. 328 km2Largest school district in British Columbia 27. 900+ Content authors across school and district staff 28. Why a mobile app? 29. Sources: ICD Report: Always Connected: How Smartphones and Social Keep Us Engaged March 2013 30. Smartphone usage181.4In 2013 million smartphone users in the United States57.3%Thats entire populationSources: ICD Report: Always Connected: How Smartphones and Social Keep Us Engaged March 2013of the 31. Smartphone usage By 2017, that will increase to222.4 67.8% millionOr populationSources: ICD Report: Always Connected: How Smartphones and Social Keep Us Engaged March 2013of the entire 32. Mobile traffic to the District 33. Mobile traffic to the District87%of mobile traffic 34. Crumpled notice syndrome 35. Good existing content 36. How we got started Establish scopeIdentify audienceTechnology choiceDesign principles 37. Whats relevant to me? What do I have to know about? What would disrupt my day? Parents at the Surrey School DistrictCredit: iStockPhoto 38. Goals: Improve communications with parents 39. Goals: Establish a first step into mobile (iOS)Today 40. Goals: Leverage existing SharePoint content and authoring process 41. Goals: Use existing skillsets for design, development and maintenance 42. Goals: Build for extensibility and growth 43. Demo 44. Considerations 45. Same content, new context 46. Coach authors on the mobile experience 47. Be mindful of notifications 48. Plan launch strategies 49. Soft launch: until Juneth 30 50. Official launch: Sept 2013 51. Technical considerations 52. Working with an existing solution 53. Abstracting/extending SharePoint 54. Working with PhoneGap 55. Device/OS considerations 56. iOS ecosystem Urban Airship: for push notifications TestFlight : for app distribution during UAT 57. 3 things to take away 58. Complex landscape but theres a just right approach. 59. Mobile second can be ok too. 60. You can extend SharePoint content to mobile apps. 61. Educate. Plan. Pilot. 62. Questions? 63. Wrap up Survey and feedback Next webinar: responsive web design in July Follow up questions are welcome! 64. Get in touch brian edwardsDirector, Portal Offerings 604.709.6201 x117mallory oconnorPractice Lead, Customer and Member Portals 604.709.6201 x114mark biceSolution Architect, Front End 604.709.6201 x119