This document discusses the challenges of mobile development and how to mitigate risks. Some key challenges include OS and device fragmentation, providing a productive user experience across devices, time to market pressures, integrating with back-end systems, security, offline usage, app distribution, and analytics. Risks include vendor lock-in, uncontrolled codebases, security flaws, complex integrations, and supporting new devices. The document recommends planning a mobile methodology to choose platforms, architectures, integration methods, and development teams to control costs and timelines.
20. Risk mitigation
methodology
noun ˌme -thə-ˌdä-lə-jē
plural meth·od·ol·o·gies
1 : a body of methods, rules, and postulates employed by a
discipline : a particular procedure or set of procedures
2 : the analysis of the principles or procedures of inquiry in a
particular field
3 : in software engineering : a framework that is used to
structure, plan, and control the process of
developing an information system
21. Risk mitigation
Planning your Mobile
Methodology
Which devices do we target?
Native, Web, or Hybrid?
Which software architecture do we employ?
How do we integrate to legacy back-ends?
How many apps do we plan to develop?
Are they customer facing or internal apps?
Who will be developing them?
What is the required time-to-market?
22. Hybrid?
Native Apps Hybrid Apps Mobile Web Apps
Native code only • Mixed code: Native & web • Accessed via Mobile
• Web code is packaged with browser
the App • JavaScript, HTML5 and
CSS3.
Native Application Native Container Mobile Browser
1001010101011101001010 Web Code
0100101011101001001101 <!DOCTYPE html
0101010100100100101111 PUBLIC Web Code
0010011001010101001010 <html>
<!DOCTYPE html
1010100101010101010101 <! - - created 2003-
PUBLIC
0101011111100000101010 12-1
<html>
1010101001001010101010 <head><title>XYZ</ti
<! - - created 2003-
1010001111010100011110 tle
12-12 - -
1010011101010111110010 </head>
<head><title>XYZ</ti
110111101000101100 </body>
tle>
</html>
</head>
<body>
</p>
</body>
</html>
Device APIs Device APIs
Platform-specific. Requires Quick and cheap to
unique expertise, expensive and develop, but less powerful
long to develop, but delivers than native.
the highest user experience.
23. Risk mitigation
Planning your Mobile
Methodology
Which devices do we target?
Native, Web, or Hybrid?
Which software architecture do we employ?
How do we integrate to legacy back-ends?
How many apps do we plan to develop?
Are they customer facing or internal apps?
Who will be developing them?
What is the required time-to-market?
25. Wrap-Up
Challenges
Creating rich mobile applications in a
fragmented technological landscape
Connecting the enterprise back-end
services in a secure and scalable
manner
Controlling the growing portfolio of
applications deployed “in the wild”
26. Wrap-Up
Mitigation
Planning development and deployment
needs in advance
Creating a organizational-level mobile
methodology
Using the right platform for mobile
development and runtime services