Your SlideShare is downloading. ×
0
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Mobile Development Challenges
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Mobile Development Challenges

2,035

Published on

A presentation outlining the challenges of mobile development in enterprise level organizations. As presented at 2011 Oracle Week Israel.

A presentation outlining the challenges of mobile development in enterprise level organizations. As presented at 2011 Oracle Week Israel.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,035
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. MobileDevelopmentChallengesNir Levy, CTO,realcommerce Ltd.nirl@realcommerce.co.il
  • 2. Agenda Challenges Risks How to avoid them Wrap-Up
  • 3. Challenges
  • 4. ChallengesOS Fragmentation
  • 5. ChallengesDevice Fragmentation
  • 6. ChallengesProductive User Experience onMultiple Devices
  • 7. ChallengesTime to Market and PressingCompetition
  • 8. ChallengesAccess to Business Back-EndSystems
  • 9. ChallengesInformation and ApplicationSecurity
  • 10. ChallengesOffline Mode andSynchronization
  • 11. ChallengesApp Distribution and VersionControl
  • 12. ChallengesUsage Statistics and BusinessIntelligence
  • 13. Risks
  • 14. RisksSolution Provider Lock-In …or worse, working with too many providers…
  • 15. RisksControlling the Codebase …in too many languages and technologies…
  • 16. RisksInformation Security Flaws thatcannot be Contained …as users simply do not upgrade…
  • 17. RisksComplex and LengthyIntegrations with LOB Systems …as they involve different development teams…
  • 18. RisksOn-Going Effort to SupportNew Devices …they just keep popping up all the time…
  • 19. Mitigatingthe Risks
  • 20. Risk mitigationmethodology noun ˌme -thə-ˌdä-lə-jē plural meth·od·ol·o·gies1 : a body of methods, rules, and postulates employed by adiscipline : a particular procedure or set of procedures2 : the analysis of the principles or procedures of inquiry in aparticular field3 : in software engineering : a framework that is used tostructure, plan, and control the process ofdeveloping an information system
  • 21. Risk mitigationPlanning your MobileMethodology 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 APIsPlatform-specific. Requires Quick and cheap tounique expertise, expensive and develop, but less powerfullong to develop, but delivers than native.the highest user experience.
  • 23. Risk mitigationPlanning your MobileMethodology 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?
  • 24. Wrap-Up
  • 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-UpMitigation Planning development and deployment needs in advance Creating a organizational-level mobile methodology Using the right platform for mobile development and runtime services
  • 27. Thank YouNir Levy, CTO,realcommerce Ltd.nirl@realcommerce.co.il

×