four steps to create a mobile strategy
DESCRIPTION
Presented in this informational webinar, Zeon Solutions and Appcelerator Titanium can help you develop mobile applications that fit all of your business needs.TRANSCRIPT
Four Steps To Create A Mobile Strategy
June 26, 2012
Today’s Presenters
Michael J. KingDirector Of Enterprise Strategy
Appcelerator, Inc.Email: [email protected]
Twitter: @mobiledatamike
Al ThompsonBusiness Development Manager
Zeon Solutions, Inc.Email: [email protected]
Ask Questions!
• Type questions in the box in the Webex control panel
• We are standing by to reply personally to your questions about issues with the webinar
• General Q&A at end of presentation
• Leading enterprise e-commerce and mobile software application development firm
• Mobile development, Software as a Service (SaaS)• Deep roots in enterprise software architecture, web
services, software life cycle• Enterprise apps, B2B and B2C e-commerce• Founded in 2003; HQ Milwaukee• Merged with Grand River January 2012• Nearly 300 employees worldwide
About Zeon Solutions
Our Mobile Expertise
• Extend mobile for business
• Integrate e-commerce, CMS, mobile with enterprise systems
• Mobile product configuration tools
• Middleware and data hubs
• Cross-platform development
• Appcelerator Gold Partner
Mobile Proof of Concept Workshop
• Stakeholder meetings to assess needs, develop strategy
• Assessment of mobile for your business
• Mobile roadmap and click-through prototype that prove business value
“By 2015, 70% of your customer interactions will originate from a
mobile device.”
Gartner Research 2011
Agenda:• What are the four steps?
• Decide how you want to interact with your mobile user• Prioritize your audiences• Choose a scalable development technology• Manage your app lifecycle
• What is the best way to time these investments?• Questions?
The Mobile Maturity Model
Mobile Web App
PROS
• Single application experience
• Enables code reuse across all OSs
• Very inexpensive to build
CONS
• Limited device specific functions, only those enabled by the browser implementation
• Performance, due to browser interpretation, will be sub optimal
• Limited functionality when offline (potential security issues with cached information)
Web UI
Limited native platform capabilities
10 Native APIs (if implemented)
One size fits all UI
Always runs in device browser
Hybrid App
PROS
• Enables significant code reuse across supported OSs
• Some device functions enabled
• Can be distributed via app stores
CONS
• Limited device specific functions, only those enabled by the platform
• Performance, due to interpretation by wrapper, can suffer
• Limited ability to adjust “look and feel” of app
Semi-native UI
30-50 native APIsAvailable (depending
on wrapper)
Application data isDelivered in HTML
Native App
PROS
• Built with the native code, no translation or emulation required; best possible performance.
• Full access to all the interactive capabilities of the device
CONS
• Traditionally no code reuse
• Expensive to produce and maintain
• Hard to enforce branding (visual elements may not be consistent)
Native UI
Full Native OSCapabilities
Interaction Priorities
Understand the use case of the application(s)
Security or usability requirements might require specific architectures
You will likely support multiple architectures for a single app/function
Agenda:• What are the four steps?
• Decide how you want to interact with your mobile user• Prioritize your audiences• Choose a scalable development technology• Manage your app lifecycle
• What is the best way to time these investments?• Questions?
Total Audience of Devices
Geographic and
Demographic Alignment
Discovery Reach + Current
Customers
Dedicated, Persistent Users
There Will Be No Dominant OS
Audience Priorities
Get to know your audiences’ operating systems and distribution needs
Understand how users are discovering and using the applications
Prioritize the audiences that will be quickest to convert
Agenda:• What are the four steps?
• Decide how you want to interact with your mobile user• Prioritize your audiences• Choose a scalable development technology• Manage your app lifecycle
• What is the best way to time these investments?• Questions?
Traditional Platform
•Connect any device to any application
•Write the app once, run it on any phone/tablet
•Connect to any database or app to create composite applications
•Most frequently based on a single application or set of apps
•Applications exist independently of each other on the device
•Limited context derived from the device or surrounding services
Traditional Platform Architecture
New Platform
•It’s not about any device, its about all of them
•Consistency of experience across devices: maintain the application’s
state, with unique device specific functions, views, and look/feel
•Data sources are both owned and public
•Sharing of information across applications via the cloud
•Information flows and permissions are infinite, based on developer
requirements
Platform Priorities
Most apps will require access to many different data sources and types
Application platforms should enable the widest reach of OSs and device classes
No one platform will be able to provide everything an enteprise will require; look for those with a wide ecosystem of SIs, ISVs and developers.
Users will require access to information, regardless of the device, and will expect the app to be intelligent about past interactions
Agenda:• What are the four steps?
• Decide how you want to interact with your mobile user• Prioritize your audiences• Choose a scalable development technology• Manage your app lifecycle
• What is the best way to time these investments?• Questions?
Manage and secure both application and data
Publish to both external app stores and to internal clients
Emulator, live device, live network and resource
Develop in one environment;optimize forIOS, Android, HTML5.
Analytics: application/user behavior
App Lifecycle Priorities
Launching an app is a commitment to:• Update and maintain• Understand and improve• Add and delete features as required
Rapid iteration and application redevelopments are the best way to keep your audience engaged
Outsourcing some aspects may be most appropriate for your requirements
Agenda:• What are the four steps?
• Decide how you want to interact with your mobile user• Prioritize your audiences• Choose a scalable development technology• Manage your app lifecycle
• What is the best way to time these investments?• Questions?
• Users will expect updates every 3-4 months
• Operating systems produce 1-2 major updates and 3-4 minor updates yearly; some app modifications may be required.
• All your application developments (in and outsourced), should utilize the same platform; enables projects to move quickly between production and maintenance
• Expect initial requirements and design phase to take 3-4 months depending on complexity of business problems
Timing and Cadence
Conclusions
Application architecture should be dictated by your app requirements rather than development methods
Audience and reach should determine operating systems and distribution methods
Development technology choices should enable:• Sourcing requirements• Audience requirements • Architecture requirements
Mobile application deployments are a commitment -- to the app lifecycle (and the costs of that cycle)
Next step: Proof of Concept WorkshopContact Zeon Solutions by June 29th – receive a free Prototype for your 1st App, Accelerate the process!• Stakeholder meetings to
assess needs, develop strategy
• Assessment of mobile for your business
• Mobile roadmap and click-through prototype that prove business value
Contact – Al Thompson, Zeon Solutions414.847.1144, [email protected]
Questions?
Michael J. KingDirector Of Enterprise Strategy
Appcelerator, Inc.Email: [email protected]
Twitter: @mobiledatamike
Al ThompsonBusiness Development Manager
Zeon Solutions, Inc.Email: [email protected]