Sp sat sv moving from web-based collaboration to the mobile arena

313 views
241 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
313
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Conclusion slide
  • From technet:http://technet.microsoft.com/en-us/library/fp161352.aspx
  • SharePoint Server 2013 offers improvements to the mobile browser experience with the introduction of a new contemporary view. Users have one of the following browsing options:Contemporary view   This view offers an optimized mobile browser experience to users and renders in HTML5. This view is available to Mobile Internet Explorer version 9.0 or later versions for Windows Phone 7.5, Safari version 4.0 or later versions for iPhone iOS 5.0, and the Android browser for Android 4.0 or later versions.Classic view   This view renders in HTML format, or similar markup languages (CHTML, WML, and so on), and provides backward compatibility for mobile browsers that cannot render in the new contemporary view. The classic experience in SharePoint 2013 is identical to the mobile browser experience of SharePoint Server 2010.Full screen UI   = desktop view of a SharePoint site
  • For smartphone devices only. Activated by default on select site templates (Team Site, Blank Site, Document Workspace, Document Center, and Project Site). It is available by default in SharePoint Server 2013.The contemporary mobile browser view renders in HTML5. This view is available to Mobile Internet Explorer version 9.0 or later versions for Windows Phone 7.5, Safari version 4.0 or later versions for iPhone iOS 5.0, and the Android browser for Android 4.0 or later versions.The contemporary view has a modern UI that is optimized for touch.It provides an intuitive navigation experience that allows you to move to different pages and parts of site with ease. Supports full screen UI view.
  • Browsing the web on a mobile device is now so common that it is essential that a SharePoint site should be optimized for readability and ease of use on smartphones and other mobile devices such as tablets.Previous versions of SharePoint Server included a single default mobile view that was auto-generated based on the existing site, and that default mobile view was not easily customizable. Now, with mobile channels in SharePoint Server 2013, you can render a single publishing site in multiple ways by using different designs that target different devices. You create a single site and author the content in it a single time. Then, that site and content can be mapped to use different master pages, page layouts, and style sheets for a specific device or group of devices.http://msdn.microsoft.com/en-us/library/jj862343
  • I am on the roadI am in a hurryI need to get/update specific information right nowDon’t have office working conditions
  • Show meexactly what I need toaccomplish my tasks!
  • Behave differently according to the current situation:Who I am, Where I amType of informationState of the current record
  • Behave differently according to the current situation:Who I am, Where I amType of informationState of the current record
  • Behave differently according to the current situation:Who I am, Where I amType of informationState of the current record
  • Behave differently according to the current situation:Who I am, Where I amType of informationState of the current record
  • HTML5 vs. Nativehttp://www.businessinsider.com/html5-vs-native-apps-for-mobile-2013-4?op=1
  • SharePint
  • Sp sat sv moving from web-based collaboration to the mobile arena

    1. 1. Moving from Web-based Collaborationto the Mobile ArenaNimrod GevaProduct Group Manager, KWizComnimrod@kwizcom.com
    2. 2. KWizCom Corporation• Founded in 2005• Headquartered in Toronto• Global vendor of SharePoint Add-Ons• 5000+ customers worldwide
    3. 3.  SharePoint 2013 Mobile Features Define Your Mobile Strategy Implementing your solution:What are my options?Collaboration
    4. 4. What’s new for mobile devices inSharePoint 2013? Optimized mobile browser experience Device channels Push notifications Location field type Business intelligence content Office Web Apps
    5. 5. Optimized mobile browser experienceContemporary viewHTML5 rendered viewClassic viewHTML, SharePoint Server 2010 mobile experienceFull screen UIWeb view
    6. 6. Contemporary view Renders in HTML5 Optimized for touch Supported by:IE9+ (Windows Phone)Safari 4.0+ (iPhone iOS 5.0)Android browser (Android 4.0)
    7. 7. Classic viewFull screen UI
    8. 8.  Publishing sites only One site, many designs Requires customizations(Master page, layouts, CSS)Device Channels
    9. 9. Choose a mobile experience What are your mobile usabilityrequirements? What is the level of interactiona user needs? Will an out-of-the-box experiencelike the contemporary view besufficient? Do you need a more customizablesolution / 3rd-party solution?
    10. 10. What do mobile users need ?
    11. 11. What do mobile users need ?
    12. 12. DemoUpdating a follow-up task just afterfinishing a meeting…
    13. 13. 1
    14. 14. 2
    15. 15. 3
    16. 16. 4
    17. 17. 5
    18. 18. 6
    19. 19. 22At the office I can enjoythe “portal experience”
    20. 20. But when I am out of the office..I don’t needour entire portalinside my smartphone!
    21. 21. I don’t need a long list of allthe libraries and lists in mysite!
    22. 22. I do Not need a Portal whileI am on the road!
    23. 23. This challenge is not new..Information Overload vs.Limited display sizeLimited timeA “non-office”environment
    24. 24. Task-OrientedEasy to Use!Context -Sensitive+
    25. 25. Task-OrientedLess is Better!
    26. 26. Context-Sensitive InterfaceBehave differentlyaccording to thecurrent situation (context)
    27. 27. SharePoint list menus are GenericNo matter which item type - youalways get the same generic menus(Based only on your permissions)
    28. 28. XLogic Error:Due Date < Start Date
    29. 29. Why do we see thesefields for a new task?
    30. 30. Why can I edit this taskif it’s alreadycompleted?Why can I edit this taskif it’s not assigned tome?
    31. 31. DemoTask-Oriented & Context-Sensitive Mobile UX
    32. 32. Task-OrientedFocused InterfaceContext-SensitiveLess is Better!The exactActions thatI Need!Different MenusDifferent FieldsDifferentPermissions
    33. 33. Task-OrientedContext-SensitiveDevice ChannelsNative AppBYODWhat are myoptions?OfflineHTML53rd-partysolution
    34. 34. Collaborative mobile UX or Portal?Task-oriented, Context-sensitiveBYOD strategyMaintenance strategyDevice Channels
    35. 35. Choosing the right 3rd-party solution for you Functionality:– Access to list & libraries– BI– Enables creating custom mobile solutions Web vs. Native App vs. Hybrid Requires connection vs. Offline End-User solution vs. Development Framework
    36. 36. SummaryTask-OrientedEasy to Use!Context -Sensitive+
    37. 37. Questions?Nimrod GevaProduct Group Manager, KWizComnimrod@kwizcom.com
    38. 38. Join us right after the event at the Firehouse Grill!Socialize and unwind after our day of learning.1765 E. Bayshore RoadEast Palo Alto, CA

    ×