Mobile Applications and Mobile Strategies for Enterprise Consumer Apps
1. Mobile Applications and Mobile
Strategies for Enterprise and
Consumer Apps
Presented by:
Kevin Benedict, Mobility Analyst
1 Netcentric Strategies - 2012
2. How Important Is Mobility to Your
Future Success?
Critical 44%
Not Important
Very 36%
Important
Somewhat Important
Important 15%
Important
Series1
Somewhat 4%
Very Important
Important
Critical
Not 1%
0% 10% 20% 30% 40% 50%
Important
Netcentric Strategies' Enterprise Mobility
2
Survey 2011
3. Planned Mobile Apps
• 88% are implementing mobile apps
• 32% - 5 or more mobile apps
insiderRESEARCH Special Report
Mobile Outlook 2012
3 Netcentric Strategies - 2012
4. What Enterprise Mobile Apps?
1. Sales/CRM
2. Workflows
3. BI Reports
4. Field Services
5. Social Enterprise Apps
6. SCM
7. POD
8. ECM
9. Inspections
10. Documents
insiderRESEARCH Special Report
Mobile Outlook 2012
4 Netcentric Strategies - 2012
5. What Mobile Devices?
insiderRESEARCH
Special Report
Mobile Outlook 2012
5 Netcentric Strategies - 2012
6. Does your company support the use of
"personal" smartphones or tablets for
enterprise mobility applications?
59% Yes
41% No
6 Netcentric Strategies - 2012
7. Field workers – What is Required
7 Netcentric Strategies - 2012
8. Mobilizing ERPs and Business Solutions
Extending back office systems to mobile workers is a top priority.
9. Mobile Social Enterprise and
Collaboration Solutions
• Convo
• Chatter
• Jive
• Yammer
• SAP StreamWork
• Google Docs
10. Mobile BI
Command and Control at the Point of Biggest Impact
10 Netcentric Strategies - 2012
11. M2M, Remote Sensors, and the
Internet of Things
Machine to Machine (M2M) systems that collect data wirelessly from small
embedded chips is changing many monitoring and tracking processes.
12. B2C – Business to Consumer
Mobile consumer devices and apps
are showing the enterprise how it is
done.
12
13. Mobile Implementation Models
• Model #1: Developing 1 app for employees to run on
1 kind of company-issued device
• Model #2: Developing many apps for employees to
run on 1 kind of company-issued device
• Model #3: Developing 1 cross-platform app for
employees to run on a wide variety of devices
• Model #4: Developing many cross-platform apps for
employees or customers to run on a wide variety of
devices
13 Netcentric Strategies - 2012
14. Challenges to Developing a Mobile Strategy
The four biggest challenges:
1. Developing a mobile strategy
2. Identifying and prioritizing
business cases
3. Choosing a platform and mobile
technologies
4. Budgeting
14 Netcentric Strategies - 2012 insiderResearch Mobile
Outlook 2012
15. Mobile Strategies?
insiderRESEARCH
Special Report
Mobile Outlook 2012
15 Netcentric Strategies - 2012
16. Rank how challenging these issues are
for your company.
1. Integrating with backend systems
2. Developing a comprehensive enterprise wide mobile strategy
3. Selecting the right mobile application development platform
4. Selecting the right development strategy for apps -Native, HTML5 or Hybrid
5. Cross-platform support (iOS, Android, Microsoft, Blackberry, etc)
6. Selecting the right MDM/MAM platform
7. Finding mobile experts and resources
8. Selecting the best mobile app vendors
16 Netcentric Strategies - 2012
18. Current State
• 41.6% of survey respondents plan to deploy more
than 6 enterprise mobility applications.
• 78.6% of survey respondents will be integrating with
multiple back end systems.
• 51.3% have no mobility policy in place.
• Only 39.8% of companies have a strategic enterprise
mobility plan in place.
19. Are you developing mobile B2C apps?
Yes No
52.5% 34.4%
19 Netcentric Strategies - 2012
20. How will you develop B2C apps?
Development Strategy Responses
Develop In-house 19.2%
Outsource Development 24.5%
Mixture of Both 38.5%
Don’t know 22.8%
20 Netcentric Strategies - 2012
21. Mobile Frameworks, Platforms and Management
• Mobile architectural frameworks
• Mobile infrastructure and integration frameworks
• Mobile user interface and experience frameworks
• Mobile operating systems and development environments
• Mobile device and M2M management
• Network Centric Operations
• Mobile application management
• Mobile user management
• Mobile security management
• Mobility governance
• Mobile Workflows
• Wireless network communications
22. What are MADPs?
• Mobile Application Development Platforms
– Integrated development environments (IDEs), templates, forms
builders, and libraries
– Support for developing once and deploying to many different
tablet and smartphone operating systems such as iOS, Windows
Phone, Blackberry, and Android
– Wireless connection management
– Support for online or offline mobile apps (mobile client data
storage)
– Data synchronization
– ERP, database, and business application integration between
mobile apps and backend systems
– Mobile app deployment
22 Netcentric Strategies - 2012
23. The role that the MADP plays
• Rapid design, development, and deployment of
cross-platform apps
• Efficient support of multiple mobile
devices, mobile applications, and mobile
operating systems
• Publishing and deployment capabilities across
mobile operating systems
• Enterprise-grade security
• Data integration capabilities with backend ERPs
and other business systems
23 Netcentric Strategies - 2012
24. Vision
1. Endless numbers of mobile applications and mobile/M2M devices
2. Integrated backend systems connected to mobile solutions (B2E and B2C)
3. Visibility, accountability, compliance monitoring
4. Real-time business intelligence
5. Location, business and context aware solutions
6. Social enterprise and collaboration solutions on mobile devices
7. Re-engineer processes to utilize these new capabilities
8. Develop decision making tools for real time management
9. Networked Field Operations – unified views
***BUILD SLIDE***Kony’s products consist of 3 sets of offerings:1. [ Advance the slide ] Our award-winning KonyOne Platform gives you write-once, run everywhere capability for mobile application development & deployment. We’ll cover the details of this product in a moment but briefly, our platform is open & standards-based, delivers the broadest and deepest multi-channel support and is the only mobile enterprise application platform (MEAP) that gives you integrated B2C and B2E functionality – and we’ll explain what we mean by that in a moment.2 [ Advance the slide ] Next we offer pre-built mobile apps for key B2C and B2E use cases and industries, including healthcare, financial services, retail, travel & hospitality, CRM and HR. These apps are feature complete but also extensible and configurable so that you can take the functionality we’ve provided and customize it, tailor it, and add any additional features you may need. 3. [Advance the slide ] In addition to our platform and apps we offer mobile application management, which enables IT directors to not only develop and deploy great mobile apps – either leveraging our pre-built apps or building from scratch – but to also provision, update, manage and secure those apps in both B2C and B2E scenarios.
***BUILD SLIDE***Full Script – When pressed for time make sure you cover items in bold text at a minimum.1. First screen: Orange layer of boxes. The first thing we want to show you is what we call Kony’s foundation layer. These are all of the different capabilities that are foundational to our platform.To the left you see our cross-platform API. Today it’s a Lua-based API but we are fast moving to a Javascript API which we’ll discuss more in a few slides. This API covers UI/UX and device features – so something like a GPS or an on-device camera can be controlled with this API. Another example would be a utility, which might be something like internationalization.Just to the right you’ll see our platform-specific properties. These are extremely important because they enable you to build apps that really take advantage of the unique capabilities of each device, that you can render in a very platform-specific way. For example there’s a feature of iPhones that gives you the unique ID of that iPhone and Kony’s platform has the ability to access that through our platform specific properties.Next we have the Foreign Function Interface, or FFI. And this is one of the ways our platform is very open, we use FFI to let you access third-party capabilities for things like bar code scanning, or a security library, or a new device like a barometer for measuring the weather, and incorporate them into your mobile app.And lastly in the foundation layer we have connectors to backend enterprise systems such as SAP, Siebel, Oracle, etc. We let you utilize native connectors for systems like SAP , Siebel, Database, etc. We also allow you to connect via Web Services or allow you to reach over 300 backend systems via our iWay enterprise connectors – so lots of options here.2. Advance the build to layer in the blue row of boxes.Conceptually above the foundation layer are the Kony components. The first two of these elements are KonyOne Studio, this is an IDE where you build your app, and KonyOne Server, which is the middleware or run-time server where the app executes.In the KonyOne Studio, you’ve got a Form Designer where you can lay out your app, a script editor, an event editor that lets you determine how your app will react to specific events so you can define what happens when the user presses a button, for example. It includes service definition so you can do things like invoke a service and determine what happens when a value comes back from a service – how do you render it etc. and map it to the UI. There are many more capabilities of the KonyOne Studio – this is a just a set of some of the highlights.Now, the KonyOne Server gives you another important set of capabilities. So for example you can have it detect the device you’re pushing the app to, to access device specific properties – remember we support over 9,000 devices and that’s constantly updated as new devices come out. We give you alert and notification services here too, not to the device like an SMS message but straight to the app, to give you that control. And we’ve got a flow controller so if you invoke 3 or 4 different services in serial or parallel you can control how everything comes back, marshall it, put it all back together, etc. and just like with the Studio, there are actually other capabilities in here that we don’t have room for on this slide.Another important component is the Kony Sync Server, which gives you the ability to create offline applications that can synchronize with backend data sources and keep a local copy of the data so that if the app goes offline – let’s say for example the user is in their car or is a technician fixing an elevator – the app can access the data locally and doesn’t need to fetch anything over the air.And lastly our components include mobile application management, which gives you both web-based and device-based capabilities for provisioning and managing your mobile apps. Our mobile application management uses a server-based admin portal for administrators to deploy and manage apps from a central console, and in a moment we’ll take about how those apps are delivered in a secure container on each device. The other important capability of the mobile application management component is the Enterprise App Store, where you can position your apps for users to browse and search for and access easily. 3. Third screen – Green and Orange boxes with Kony Build Screen in betweenOK so after you’ve built your application you’re ready to generate a version of it that you’ll want to test, and you can see here all the choices and flexibility our build screen gives you. You can really see all of the different types of outputs you’re able to generate from the application that you’ve defined in the Studio. So for example, after you’ve designed and built your application you’re able to generate what is absolutely the widest range of support for devices in our and channels in our industry. So the first thing you could do, for example, is decide you want to output in native mode, and here you see you can do that for all of these 7 platforms in the green box, iOS all versions, Windows Phone 6.5 through Mango, Android all the way up from 1.6, Blackberry all the way from version 4, even feature phones, J2ME phones we’re able to generate native output. We do this in 2 ways: first is we generate human-readable native source code using our libraries and our SDK to do that – this is another of the ways we’re an open platform. The other option is we’ve got a Lua VM today and we’re replacing that with a Javascript interpreter, so what we do here is we’ll take Lua-based byte codes and generate binaries that are unique for each device. We’ve got a VM that is packaged with our byte code and you get very high performance native apps out of that.Now what we can do here that is absolutely unique in the industry is that simultaneously, from the same single code base, you can build any part of your app to be mobile web, as we show here in the orange box. So here we have highly advanced mobile web support for everything from HTML5 to basic HTML. And there are several deployment models we support with mobile web. One is straight mobile web, another is single page application (SPA) model, which in many cases gives you snappier performance. We also support what the industry calls hybrid – which means a mobile web app that is wrapped in a native app shell to look and act more native, and what we call mixed mode, which is an app that interchanges native and mobile web forms as needed.So here’s where you can see the extreme flexibility of the Kony technology – from a single platform and single codebase you can literally mix and match whatever outputs you need for your app. So as you’re building your form you can say this will use native, or you can say this will be HTML5, whatever you need to make the app really work for your needs and you don’t have to compromise by wrapping the app or anything like that if you don’t want to. So there may be HTML5 code you want to repurpose for part of your app, but then you want to leverage native capabilities for another part.4. Advance the Screen – should layer in blue row of channels and images of devices.Last but not least, you can see all the channels our products support. We support smartphones, tablets, Windows 32 desktop, kiosks using Windows Presentation Foundation, to even feature phones and finally desktop web, which is where we’re working on additional capabilities we’ll talk about in our roadmap section.5. Wrap UpSo we’ve covered this a bit as we walked through this architecture, but important to stress that Kony delivers an absolutely standards-based, open and universal platform.For standards-based, we have:Platform infrastructure based on Java and industry standard database technologies Platform supports Java Enterprise Edition, W3C HTML standards W3C Extensible Markup Language (XML), HTML 5, XPath, XML-RPC, the Simple Object Access Protocol (SOAP), and RSSFully integrated application delivery solution incorporating application development, testing, deployment and delivery to devicesIDE utilizes industry standards & standard APIsFor open, we have:Combination of cross platform API, platform specific API & FFI (Open) enable flexibility and powerful range of development options – developers don’t have to settle for the least common denominator of container apps – Only Kony Has This CapabilityFor universal, quite simply Kony is the only MEAP on the market that combines full B2C and B2E capabilities and provides a single codebase for write-once, run everywhere capability.
Our differentiation: (1) Custom widgets that can be dragged + dropped in the Kony IDE. (2) Leverage integrations that other third party groups offer, i.e. Partner custom widgets that can be imported into application development projects and be re-used.
Reps: Talk briefly about the importance of mobile application management especially in B2E environments and move on. SEs can talk in more detail to the graphic and specific features called out here.