The interactive mobile application market is estimated to reach $15 billion by 2013. This presentation shows how to be prepared from an infrastructure, resource and strategy perspective. We'll explore the different types of mobile applications an enterprise may pursue, technologies used to develop them, and explore scalable backend architectures that can stand up to the higher demands of mobile computing.
Interactive Mobile Applications in the Enterprise: Are You Ready?
1. Interactive Mobile Applications in the EnterpriseAre you ready? Matt Van Bergen Principal, CTO mvanbergen@citytechinc.com 312-673-6433 x111 September 22, 2010
2. Abstract Interactive mobile applications can serve your users and customers in ways that traditional web-based applications cannot. Interactive mobile applications enable you to have a consistent and ongoing interaction with your users, allowing them to be more engaged and committed to your service beyond what is possible with a mobile web browser. Being an IT leader in your organization, you must be ready to field questions and, as necessary, build applications and infrastructure to support the wave of mobile applications which will likely be demanded by your marketing, sales, operations and customer service departments. This webinar provides an overview of how you can prepare for the mobile application demands of your organization and customers.
3. Agenda What are interactive mobile applications? What’s all the fuss about? Mobile applications and your organization Top 5 ways you can prepare Case Study: Extreme Scale Reference Mobile Architecture How to be ready for your first mobile project
4. What is a mobile interactive application? Reside on the mobile device connecting organizations of all types to employees and consumers through a variety of continuous, entertainment-like contextual experiences. Browser-based Device installed
5. What’s all the fuss about? Worldwide mobile app downloads will exceed 21.6 billion by 2013 (Gartner) Revenue from U.S. mobile application downloads alone could reach nearly $1.6 billion in 2010 and would hit $11 billion in 2014 (WSJ) Employees prefer a smartphone over a laptop as their primary mobile device for trips under 5 days. Mobile applications are seen as key strategy of building an organization’s brand. Mobile applications can provide a strategic advantage. Mobile applications can be location aware and context aware. Amazon sold over $1B via their iPhone App eBay sold over $400M via their iPhone App
11. Prepare Back-end Systems for the Ubiquitous Client #1 Establish a services oriented architecture initiative. REST is the preferred method for mobile integration. Design enterprise services as coarse grained services. Secure services with SSL and Basic Authentication. Be ready to scale if your services will be available to general public (Hint: see next slide if you have doubts). Internet Services Oriented Architecture Internal Application Internal Application Database Database
14. “Cloudy With a Likelihood of Mobile” Cloud computing platforms come in a couple different flavors: Platform as a Service (PaaS) Infrastructure as a Service (IaaS) Software as a Service (Saas) Pay for usage, no need to invest in costly hardware upfront. Very important for consumer targeted mobile apps – scalability important. #2 Are you ready to scale for mobile? In one month Shazam added 25 million users Britain’s Got Talent app added 200K users in first 4 days. Skype’s iPhone app attracted 5 million users in first few days.
16. Understand the various mobile devices and their platforms #3 iPhone OS iPhone OS Symbian OS Android OS Windows Mobile OS BlackBerry OS Will your mobile applications be supported by all of these devices? Are you going to limit the supported devices to only those that are “supported” by your organization?
26. Understand Cross-platform Mobile Development (continued) #4 Example Cross Platform Frameworks Develop using HTML5, CSS and Javascript iPhone, Android, BlackBerry, Symbian and Palm support Use xCode IDE for iPhone, Eclipse IDE for BlackBerry and Android, etc. Decent device feature support Develop using HTML5, CSS and Javascript (Python, Ruby, PHP possible). More “nativeness” ( iPhone, Android and BlackBerry support Proprietary IDE. Very good device feature support Catch CITYTECH’s Jeff Schwartz’s presentation on PhoneGap at the October 18th Mobile Monday Chicago user group meeting.
28. Make security a first class citizen in your architecture Security is the #1 concern for deploying mobile transactional applications (Entrust survey in April, 2010) The end to end wireless communication chain is the most secure element in the entire mobile application value chain. The device application and user should be of focus. Traditional username and password strategies are common but also very vulnerable. Two-factor authentication is gaining popularity. Comprehensive auditing trail and alerting based on non-standard behavior. Educate your users on security risks and new technologies as necessary Leverage best practices learned from web application development Don't persist sensitive data (unless you have to) iPhone, Android, Windows Mobile and BlackBerry devices provide remote “wipe” capability in case a mobile device is lost or stolen. Beware of HIPPA, Sarbanes-Oxley Act (SOX), Payment Card Industry (PCI), etc. Develop flexible security policies #5
29. Case Study: Extreme Scale Reference Mobile Architecture Cross platform, native mobile application (iPhone, Android and Mobile Web) Back-end services hosted on Amazon EC2 Distributed, Grid Based Architecture Massively scalable High performance In-memory storage Technologies Used Red Hat JBoss InfiniSpan Red Hat JBoss AS Red Hat JBoss Modeshape Amazon EC2 Cloud Amazon S3 Cloud Persistence PhoneGap cross-mobile development framework
30. Case Study: Extreme Scale Reference Mobile Architecture
31. Your First Mobile Project Start with a small project. Consider the level of security required. Leverage existing backend services that are available elsewhere in your enterprise – take abuilding block approach. Know your users’ target mobile device(s) Load test the backend services before going live (especially for a consumer mobile app). Emphasize superior user experience
32. About CITYTECH Professional Services: Specializing in the design, development and execution of highly available and scalable enterprise applications Consultants: Average experience of 10 years Offices: Located in downtown Chicago, IL Goal: Strive for long-term partnerships with partners and clients Contact CITYTECH to setup a no cost onsite needs assessment to see how prepared your organization is for mobile interactive applications. Matt Van Bergen Chief Technology Officer 312-673-6433 x111 mvanbergen@citytechinc.com http://blogs.citytechinc.com/matt http://twitter.com/mvanbergen Web: http://www.citytechinc.com Twitter: http://twitter.com/citytech Blogs: http://blogs.citytechinc.com 211 W. Wacker Drive Suite 1300 Chicago, IL 60606
Editor's Notes
Maybe give an example for brand building using mobile apps – GEICO Insurance introduced an iPhone app in December 2009 to extend its brand and reach new and existing customers with its GloveBox application. “We know that customers of all ages are users of the iPhone,” Mr. Reed,hief information officer and vice president of Internet business at GEICO, said. “We really want to accommodate the customer’s ability to access our services no matter the age demographic.”
m-Commerce – quench consumer’s hunger for a gut purchase, given context and proximity
Create diagram that shows iPhone/iPad device talking through the SOA fabric and connecting to SalesForce for lead creation and WCM for web content.
Maybe split this into 2 slides with the “Are You Ready for Mobile” content on the next slide?
Two--factor authentication: involves “somethingyou have,” such as a token/usb key, and “something you know,” suchas a PIN or password. Hardware tokens provide a uniquepasscode each time a user logs in to the system. Tokens areportable, easy to use, relatively inexpensive, and compatiblewith virtually every type of computer.Develop flexible security policies: Don’t over engineer security policies for application that don’t require it while make sure you have the correct security in place for apps that access top secret enterprise systems.