Mobile Application & Wireless Strategy

817 views

Published on

Considerations and best practices for design, development and deployment

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
817
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • When it comes to mobility, there is a LOT to think about.
  • The 6% are actually the naïve ones; enterprise mobility is hard
  • Operators — These are the wireless network providers, typically telcos. Examples include T-Mobile, Verizon Wireless and the largest being China Mobile with 436.12 million subscribers. There were no Canadian operators in the top 15. (As of Feb 2010 Canada has 22.452 million* subscribers) Wireless network providers are often called carriers.They build the cell towers.They operate the network.Examples include T-Mobile, Verizon Wireless, Rogers, etc.NetworksThe operators operate the wireless network. Wireless networks come in different varieties, i.e. 2G - GSM, EDGE, 3G – CDMA, UMTS, 4G. There are many types of wireless networks.2G – GSM, EDGE, etc.3G – CDMA, UMTS, HSPA, etc.4G – LTE AdvancedDevicesCell Phones or Smart phones. The industry calls them handsets or terminals. Feature phones make up the largest group with over 3.5 billion devices world-wide in 2008. Approx. 85% are feature phones. Smartphones make up the smaller group. PlatformThe platform provides access to the device via a core programming language.3 categories of platforms:Licensed – Java ME, Windows Mobile, LiMoProprietary – Palm, BlackBerry, iPhoneOpen Source – AndroidGONE IS THE WORLD OF THE LOCKED DOWN PC, IMAGED FROM IT AND DELIVERED WITH GOVERNEROR ON ITOperating System provides core services or toolkits that allow applications to talk to each other and share data or services. Examples include Symbian, Windows Mobile, Palm OS, Linux, Max OS X, Android. The Application Framework is used to create applications. Frameworks are well standardized – devices are not. Examples include Java, Android SDK, Cocoa Touch , WebKit, Web Runtimes (WRTs) Services are what you interact with be it sending a text, using the GPS in Google Maps to determine a driving route, or using a custom CRM to locate a client contact record.There is a LOT of room for failure in all of these layers which make mobile development extremely challenging. The task may be comprised of accessing several applications, i.e. looking up a name in a CRM and then calling the client on the phone. Applications are what a programmer has developed to do “something”, i.e. a time reporting app, a game, etc. Services are a more generic term that defines a task a user is trying to do. Device Fragmentation is a major issue from a developer’s perspective. When a device is sold to an operator, it is customized to their requirements. In the BlackBerry smartphone example in Canada –Rogers, Bell, TELUS, SaskTel, MTS, Wind Mobile, Mobilicity, plus several others. For EACH device for EACH operator, you will likely have a customized OS. At Kryos, we have 5 separate build packages to support the different OS versions and device platforms for the BlackBerry Smartphone. We automated our build process using MAVEN due to the time it was taking to manually compile all of the various .JAD files required to support 4.2 & above of the RIM OS. - 7 of the 18 Android phones never ran a current version of the OS.- 12 of 18 only ran a current version of the OS for a matter of weeks or less.- 10 of 18 were at least two major versions behind well within their two year contract period.- 11 of 18 stopped getting any support updates less than a year after release.- 13 of 18 stopped getting any support updates before they even stopped selling the device or very shortly thereafter.- 15 of 18 don’t run Gingerbread, which shipped in December 2010.- In a few weeks, when Ice Cream Sandwich comes out, every device on here will be another major version behind.- At least 16 of 18 will almost certainly never get Ice Cream Sandwich.Dream of days of os/2, windows and mac and think life was easy
  • Retire -- bYOU
  • Mobile solutions sit on top of a complex stack of technology. How strong is the foundation?Are your core business systems ready for the unique requirements of a mobile solution?
  • What is a full mobility strategy consist of: roadmap over time; governance rules, stated deployment; upgrade of critical path systems.
  • Key Issue: How will mobile technologies and platforms evolve through 2015 ?HTML5 is a draft specification for browser behavior and capabilities that likely won't be final until mid-2013. A de facto standard set of features has already appeared in a range of popular browsers, including those from Google and Apple. Microsoft is behind the curve in HTML5 support, but promises full support in Internet Explorer 9.HTML5 makes the browser much more powerful. Including new markup tags that make it easier for programmers to design for search engine optimization, support for local storage, rich media types such as video, audio, scalable vector graphics and a low-level "canvas" reminiscent of early software-based graphics renderers, HTML5 makes it possible for the browser to become a full-fledged application container even when disconnected from the Internet. Support for location-based services enables the browser to become an interesting platform for mobile applications, and features like background threads (via Web Workers) and lower-level networking support (via Web Sockets) creates the potential for faster, more responsive Web applications.The implications for developers are clear: the browser becomes more important than ever before, and proficiency with HTML and JavaScript, the lingua franca of the browser, will follow. What of "heavy RIA" technologies, such as Flash, Silverlight and JavaFX? Gartner expects these technologies to be under pressure to find new ways to innovate to justify their existence. However, it is already clear that there are imperfections in the HTML5 specification that can be exploited. For example, HTML5 does not provide support for DRM, a key feature for content creators and publishers. HTML5 does not support accelerometers and web cameras in mobile devices, so applications like Apple's FaceTime can't be delivered in a browser. Gartner expects leading heavy RIA vendors to maintain a pace of innovation that keeps them relevant, but for a gradually shrinking percentage of Web applications. Most enterprises will be satisfied with HTML5 alone.
  • The amount of time spent interacting with data (entry) on … 30 seconds – A smartphone3 minutes – A tablet30 minutes – A laptop
  • Mobility Maturity ModelReactive DeploymentMobile devices for CXO’s, managers, sales personnel, or LOB EmployeesMobile applications: Email, calendar and PIMMobility initiatives are conservative and driver by competitor activitiesProactive DeploymentMobile devices deployed to CXO’s, managers and sales professionals as well as IT and customer service organizationsMobile applications: Email, calendar, PIM as well as field service and IT applicationsMultiple devices and operating systems are used to address requirements of various business units in the organizationIntegrative DeploymentMobile Devices are deployed to executive assistants, Use a corporate mobility strategy leveraging multiple mobile platforms to support mobile application requirementsMobile solutions are key strategy initiatives. Mobile applications address many different organizational business unitsAnother view of how organizations see themselves with regards to mobility is the data captured from the Mobility Manifesto at http://www.mobilitymanifesto.com. Data as of Feb. 8, 2012. Mobile Savviness:A measure of the organization’s expertise and experience in mobility today, including: How widely used is mobility inside your company?How many smartphone and tablet platforms does your company support?Does your company support BYOD policies?How expert is your IT department at managing mobile devices?How well does your company use mobile apps?Mobile Culture:A measure of your company’s ambitions towards mobility and its grasp of the transformative opportunities, including: How your company ranks against peers?How progresssive is your company’s BYOD policy?How mobilized are key facets of your business such as supply chain and sales?Laggards:A company that lacks the ability to use mobility to its advantage today and has little desire to change this. Smartphones come in the guise of BlackBerrys, with iPhones and Android devices not even a blip on the radar. Rookies:A company that understands the advantages to a more mobile workforce but has yet to act in any serious way to benefit from these. Some basic mobility geared initiatives, like in the form of BYOD policy or multiple platform support, but little that suggests a long-term strategy. Dreamers:This is a company that talks the talk but has a little way to go before it walks the walk. With mobile policies, BYOD initiatives and perhaps even enterprise app stores in place, this company is thinking big. What has been lost on the way are smaller yet integral aspects such as employee mobile reimbursement programs, long-term mobile strategies and 360-degree devices security. Leaders:A company with employees that is set up for success from day 1 due to its approach to mobility. Smartphones, tablets and a fully accessible and secure file system from wherver you choose to work are just some of the benefits of working at a company like this. So is the use of mobile enterprise apps that tangibly cut costs and labor and/or boost revenues.
  • Test your mobile apps in context. If the data entry for a field application is tested only while you are sitting at a desk, you cannot anticipate or get a “feel” for how it will really work in the field. You may find that a third-party data collection device could significantly enhance the data entry process (bar code scanners to collect equipment info first and then the data entry that can’t be collected in that manner).
  • Mobile Application & Wireless Strategy

    1. 1. Mobile Application & WirelessStrategyConsiderations and best practices for design,development and deploymentTrevor NimegeersPresident and CEOKryos Systems @trevornim Brought to you by: 1
    2. 2. Intro 17 years running a niche in consulting / integration firm focused on enterprise customers Internationally Award winning team with deep specialties in SOA, portals and mobility 2009 launched a mobile software company, built Platform for Enterprise Apps: Velocity Team of specialists in Calgary & Toronto Dad of 4, avid skier and Scouter @trevornim /trevornimegeers trevor@kryos.com 2
    3. 3. Topics for Today: Challenges with Mobility Where a Strategy makes sense Questions you should ask Architecture Approaches Mobile Apps Examples 3
    4. 4. Does your Mobility Strategy look/feel like this?Source: http://blog.prnewswire.com/2010/11/22/jenkins-is-it-the-year-of-mobile-pr-yet/ 4
    5. 5. Barriers to increased mobilization Security features and security management 54% Application integration complexity 47% Device management (e.g. software installation, software updates, lost devices) 46% Service Pricing (data plans) 44% Application development complexity 37% No perceived business advantage / insufficient value 15% Job redefinition to take full advantage of capabilities 13% We do not see any significant barriers 6%Base: 535 respondents deploying or planning to deploy mobile applications on smartphonesData: InformationWeek Analytics Application Mobilization Survey of 695 business technology professionals (December 2009) 5
    6. 6. The Mobile Ecosystem Applications & Services Application Frameworks Device Operating Systems Fragmentation Platforms Devices Networks Operators A mobile strategy will help minimize the risk associated with device fragmentation. Device fragmentation can make application delivery & support very challenging.Source: Fling, Brian. Mobile Design and Development. OReilly Media, 2009. 6
    7. 7. Bring Your Own Device / BYOD 7
    8. 8. 8
    9. 9. Enter Mobile Device Mgmt (MDM) More than ½ of all users don’t lock their devices Almost 1 in 5 devices are lost each year Mobile devices are predicted to be the new malware frontier There is a policy disconnect between IT and end users Can you protect your mobile fleet against cost overruns, loss/theft, abuse & international roaming etc. 9
    10. 10. MobileApplication Strategy 10
    11. 11. Do you need a mobile application strategy?Strategy less Strategyimportant – important –Opportunistic StrategicApproach to Approach toMobility Mobility 11
    12. 12. Decisions, decisions. Who owns the device? Standardize on a device and/or a platform – or not? Do you want a rich experience tied to a platform or generic experience that makes device fragmentation less of an issue? What are your security policies and risk tolerance levels? How will you evaluate success? Consider your user demographics. Consider your available technical resources. 12
    13. 13. What should your mobile & wirelessstrategy address? Vision of the mobile workplace for the identified mobile user profiles Road map for mobile initiatives Architectural approach to development Mobile Application Management Mobile Device Management 13
    14. 14. Choosing an architectural approach … “ With mobile applications, its not a one size fits all -- it depends on the problem youre trying to solve, the region of the world youre in, the customers that youre dealing with ... ”Source: Bob Schukai, Global Head of Mobile Technology, Thomson Reuters 14
    15. 15. The Slope of Interactivity 15
    16. 16. Which Approach for which Apps? 16
    17. 17. What architectural approachshould you use for development? Gartner predicts that in 2010, 50% of enterprises will have migrated away from tactical mobile application silos (supporting a single application) to strategic platforms that can support multiple applications, manage devices, and secure data and transport. 17
    18. 18. Mobile Strategy Deliverables Increasingly Complexity and Customer ValueMobile Application Strategy App Mgmt & LOB EnterpriseEngagement Models Getting Started Tech Assessment Road Map Road Map Education – where does Technology – a preliminary Enterprise-wide focus tying Single line of business mobileFocus of the deliverables opportunity lie with mobility mobile app strategy may application strategy mobile application strategy to for the enterprise? already be in place business objectivesDeliverables Services Road Map   Duration of Road Map 12 months 18-24 months Strategy Initiatives Report   Strategy & Related Initiatives  Dependency Tree Technology Recommendations Report    Governance Recommendations Report    Initial Phase Project Plan   Readiness Assessment Report  Executive Presentation     Visualization Mockups       Pilot / Mockup Mobile App Mockup Mockup or Pilot (1) Expected Project Duration 1-2 weeks 3-5 weeks 6-8 weeks 10-12 weeks Number of interviews 3-4 (short) 4-5 6-8 12-16 Number of workshops 0 2 2-3 4-6 18
    19. 19. The importance of design “ Companies such as Apple suggest that the design of how the application looks and works should take at least 60% of the project’s time, for any new development. It is better to understand ” and get it right the first time.Source: Ian Thain, Sybase, Feb. 8, 2012 19
    20. 20. Example Application: Web vs Mobile InterfaceIn the Web world… or the mobility world! (Yes it’s the same application) 20
    21. 21. Design @ Work30 seconds3 minutes30 minutes 21
    22. 22. mobilitymanifesto.com The Mobility Maturity ModelSource: “Economic Impact Of A BlackBerry Solution In North American Enterprises”, September 2009, Forrester Consulting on behalf of RIM 22
    23. 23. Test early. Test often.Test in context. 23
    24. 24. Trevor NimegeersPresident and CEO(m) 403.620.2013trevor@kryos.comtwitter.com/trevornimwww.kryos.comwww.kryosvelocity.comtwitter.com/kryosvelocity 24

    ×