The document discusses the challenges and trends in developing cross-platform mobile applications, particularly in relation to various operating systems and the increasing smartphone market. It highlights the importance of native applications and the complications of platform fragmentation, marketing, and legal issues. Additionally, the potential of HTML5 is explored as a solution for mobile app development and the specific considerations when integrating with SharePoint 2010.

1. Enabling cross platform mobile applications.…that also work with SharePoint 2010.Communardo Software GmbHChristian Heindel

2. 2.250.000.000 Tooth brushes in use4.617.136.636 Mobile phone subscriptionsSource: http://www.slideshare.net/hirsch30/economics-of-apps-university-of-oxford-15-oct-201091% of people have their mobile within arm’s reach 24/7. (Morgen Stanley 2007)Facebook mobile audience now at 250M users! Was 65 million in Sept 09. (03/2011, http://www.zdnet.com/blog/facebook/facebook-passes-250-million-mobile-users-mark-overhauls-mobile-site/1079)39% of SmartPhone Owners use their devices in the bathroom. (http://tcrn.ch/ifCSC8)SmartPhone PeakGfK study: http://www.gfkrt.com/news_events/market_news/single_sites/007090/index.en.html

3. AdFonic statistics: http://www.bmob.co.uk/2010/11/15/sofa-and-bed-surfing-on-the-rise/Facts from the intro…2VIDEO:http://www.youtube.com/watch?v=CjUcq_E4I-s

4. The challenge:Large number of different target platforms.

5. No clear market leader, like with desktop OS.

6. Endless list of manufacturers and devices.Platforms for mobile devices:MeeGo (MobLin+Maemo) (Intel/Nokia), Android (Google), iOS (Apple), WebOS (HP), WindowsMobile, Windows Phone (Microsoft), BlackBerry OS (RIM), Symbian, Bada (Samsung), Qt, J2ME (Oracle), Brew (Quallcomm)In addition, netbooks and tablets also run:Windows, Linux, OS X, Chrome OSIntroduction3

7. iPadIt changed everything... Chromebookhttp://www.google.com/chromebook/Windows 8 will run on ARMSay hello to Windows 8 tablets…HP webOS netbooksSource: "CES: Microsoft shows off Windows 8 on ARM.", ZDNet, http://www.zdnet.com/blog/microsoft/ces-microsoft-shows-off-windows-8-on-arm/8339, http://www.engadget.com/2011/05/18/evidence-of-webos-netbook-and-keyboard-less-phone-pop-up-in-deve/ , http://www.golem.de/1106/84073.htmlEverything changes…4

8. Market share by OS from 2007 to 2011 according to Gartner Inc.Worldwide Mobile Device Sales14,4-19,9% of all mobile devices sold in 2010 were smartphones.This was an 72% increase from 2009 to 2010.Sources: http://www.gartner.com/it/page.jsp?id=1543014, http://www.gartner.com/it/page.jsp?id=1306513, http://www.gartner.com/it/page.jsp?id=910112, http://www.golem.de/1106/84073.htmlMarket shares5

9. Market shares Q4 / 20106Sources: Canalys (http://www.canalys.com/pr/2011/r2011013.html), Wikipedia (http://en.wikipedia.org/wiki/Mobile_operating_system)

10. Source: http://en.wikipedia.org/wiki/Mobile_operating_systemFragmentation7

11. MarketingPresence in App Stores is good for visibility of your product.

12. This is important for consumer products, not so much for enterprise products.Performance, Look & FeelNative applications run faster and integrate better.PossibilitiesBrowsers do not get access to all functions, like phonebooks, camera and so on…PRO native applications8

13. Incalculable business risksWill the application be approved by the platform lord?

14. How long will it take?Legal stuffA lot of contracts and rulesA lot of work / costsTry publishing to the following stores at the same time: App Store (Apple), Android Market (Google), Amazon Appstore for Android, BlackBerry App World (RIM), Ovi Store (Nokia), HP App Catalog (WebOS), Windows Marketplace for Mobile, Windows Phone Marketplace (Microsoft), Samsung apps

15. Fees for app stores usually around 30% of revenue.

16. You need specialized developers for the different plattforms.

17. You need to rely on frameworks like PhoneGap, RhoMobile, AppCelerator

18. You will not be indexed by search engines.CONTRA native applications9

19. HTML5 totherescue10Source: http://www.w3.org/html/logo/

20. Whatsomeunderstand:Objective C (iOS)

21. C#, XAML (Windows Phone)

22. Java (Android)

23. Qt (C++) (Symbian, Maemo)What everybody understands:HTML

24. JavaScript

25. CSSProgramming languages on mobile platforms11

26. Mobile platforms with A-grade browsers:Apple iOS 3+

27. Android 2.1+

28. BlackBerry 6+

29. Windows Phone 7.5 ‚Mango‘, in fall 2011Those represent 95% of US internet traffic from mobile devices.They supporting features like:Web fonts

30. Geolocation API

31. Offline web applications

32. Web SQL databaseSources: http://www.sencha.com/products/touch/, http://caniuse.com/, http://developer.yahoo.com/yui/articles/gbs/, http://www.zdnet.com/blog/microsoft/microsoft-to-support-same-ie9-security-privacy-features-on-phone-and-desktop/8706Mobile browser support12

33. The Google Font API works reliably on the vast majority of modern mobile operating systems, including Android 2.2+ and iOS 4.2+ (iPhone, iPad, iPod).Source: http://www.google.com/webfontsExample: Web Fonts13

34. Example: Geolocation API14

35. W3C published first draft of HTML in 1993

36. HTML 4.01 published in 1999, then stagnation

37. Formation of WHATWG in 2004 (to push along HTML5)

38. W3C active again since 2006, published first draft of HTML5 in 2008

39. XHTML2 working group stopped 2009

40. Not finished. Currently published as “working draft” (04/2011)

41. W3C Confirms May 2011 for HTML5 Last Call, Targets 2014 for HTML5 Standard (http://www.w3.org/2011/02/htmlwg-pr.html)HTML5 - A vocabulary and associated APIs for HTML and XHTMLhttp://www.w3.org/TR/html5/ / http://www.w3.org/html/wiki/FAQsFocus shifted from documents to web applications.HTML5 Timeline15

42. Web Hypertext Application Technology Working Group (WHATWG)Founded in 2004 by employees of Apple, Mozilla, Google and Opera.

43. Working on HTML and APIs for development of web applications.World Wide Web Consortium (W3C)HTML working group

44. HTML5 specificationInternet Engineering Task Force (IETF)Responsible for internet protocols like HTTP

45. HTML5 WebSocket API -> WebSocketprotocolGroups working on HTML516

46. Spelled out in WHATWG specification:Compatibility

47. Utility

48. Interoperability

49. Universal accessSome proof:HTML5 is 20 years backwards compatible

50. id=”html5”, id=html5, ID=”html5” – will all be accepted

51. Separation of content and presentation via CSS3.

52. Almost all HTML formatting parameters no longer supported

53. Accessibility (WAI-ARIA roles -> Screen Readers)

54. Media Independence (different devices and platforms)HTML5 design principles17

55. Further proof:Support for all world languages

56. Everything is easier now.