Norman Smith SAIC August 15 2011 Introduction Public Facing vs Enterprise Mobile Apps The Enterprise Prospective Lessons Learned Getting Started Summary Background We started exploring CrossPlatform Mobile apps as an IRampD project with a national nonprofit organization ID: 732417
Download Presentation The PPT/PDF document "Preparing For Enterprise Mobile Apps" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Preparing For Enterprise Mobile Apps
Norman Smith, SAIC
August 15, 2011Slide2
Introduction
Public Facing vs Enterprise Mobile Apps
The Enterprise Prospective
Lessons Learned
Getting Started
SummarySlide3
Background
We started exploring Cross-Platform Mobile apps as an IR&D project with a national non-profit organization
Took cross-platform approach, which led to our Enterprise emphasis
Long Lessons Learned List
Mobile apps are not simply programs, they are systems
Mobile Enterprise Apps are different
Mobile Enterprise Apps are Cross-PlatformSlide4
Why Users Will Benefit From Mobile Apps
Mobile apps are Universal
Cross-platform
Uses all capabilities of the smartphones
GPS, camera, autodialing, menu selections, alerts, query by location
Information presentation
Lists, images, maps
Integrated with their enterprise backend systemsSlide5
Cross-Platform Devices
Phones
iOS – iPhone, Touch
Android
Blackberry
Windows Phone 7
Tablets
iPad
AndroidSlide6
Mobile Capabilities That Influence Apps
GeoLocation
PIM Contacts
Camera
Barcode
Date/Time Picker
Native Menus
Tab Bar
Navigation Bar
Signature Capture
Bluetooth
Calendar
Push
Screen Rotation
Native Maps
Alert
Audio File Playback
Ringtones
NFCSlide7
Public Facing Apps vs. Enterprise AppsPublic FacingEnterprisePlatform Specific
Frequently
No, Cross-platform
App is considered a ...
Program
System
Maintenance
Complicated for platform specific implementations
Single code base for cross-platform simplifies maintenance and support
Security
Rarely because utilize publicly available data
Enterprise data access makes security critical
Distribution
Vendor-specific App Store
Controlled via private app store, either internal or external
App Management
Not required
Minimally be able to wipe app and dataSlide8
Typical Public Facing App ArchitectureSlide9
Typical Mobile Enterprise App ArchitectureSlide10
Typical App Arch Using Rhomobile ToolsSlide11
The Enterprise Prospective
Everyone wants Mobile Apps
Today's mindset is phone-specific
Must take the Enterprise View
Cross-platform apps
Must consider security
Access corporate data
Apps must be managed
Cross-Platform means phones and tablet even
if you
don’t plan on supporting todaySlide12
NASA WebTADS Mobile AppThe ProblemAllow employees who are out of the office to enter and approve time.The SolutionA time charging application with most functionality of desktop app. Private App store. The Phone AppApps for iPhone, Blackberry, and iPad. No data stored locally.Slide13
E2I Knowledge Share App
The Problem
Create a collaboration environment for staff frequently out of office. No more e-mail to wrong people.
The Phone App
Cross-platform, private app store, basic app management included, security concerns covered
.
The Solution
App with Wiki back-end feeding data to multiple smart phone types. REST/Json based messaging. Data caching on phone
. Slide14
Mobile Enterprise Apps...
Are Enterprise-centric
Security, Data usage, Architecture
Are cross-platform
Single code base is critical for long term maintenance
Standardize on a development platform
Treated as a system
Phone/tablet is client portion
Server portion feeds data to the phone
Apps/Devices must be managed
Private App Store for selective distributionSlide15
App Management vs. Device ManagementApp ManagementDevice ManagementData Encryption
App data only
Entire phone
Private App Store
Usually
Rarely
Wipe Just App and Data
Yes
No
Wipe Entire Device
No
Yes
Remote Diagnostics
No
Yes
Policy Enforcement
No
Yes
Examples
RhoGallery
, Antenna
Blackberry BIS, Iron Mountain, SybaseSlide16
Mobile Enterprise App SecurityMust be incorporated from startCount on close examination by IT securityYou'll need a Security PlanServer may be covered by existing backup proceduresSlide17
Plan on IT Security ReviewWhat data is exposedArchitectureWhat tools are usedServer scans will be requiredHow are known issues handledPhone password handlingSlide18
Lessons Learned
Take the Enterprise View
Use light weight messaging
Build security into the app
Enterprise Mobile Apps are cross-platform
Most Mobile Apps require a back-end server to access enterprise
Development tools make a difference
Think about division of processing between device and back-end server
UI experience in simulators are different than on the device
Screens multiply like rabbits!Slide19
Prototype
Screen
MapSlide20
Standardize Mobile Development
Common Development Approach
Provide Tools – Hosted Development Portal or local
Developer Training
Back-end Specifications
JAD Session for gathering initial specs
Enables developers to move from project to projectSlide21
Getting StartedHave a planBudget for MEAP toolsIdentify an evangelistChoose a first projectSlide22
Mobile PlanVisionCross-platform or notAddress SecurityReview ToolsSlide23
Pick A FrameworkWhat tools are availableSupport for Mobile Enterprise apps?Developer skills/preferencesTool costsIs the scripting language proprietary or open source?Cross-platform?Slide24
Tool CostsPrivate App StoreApp/Device ManagementDevelopment environment Phone client (most are licensed per phone/per app/sometimes per month)MiddlewareSlide25
Identify An EvangelistDo presentationsGet people thinking about potentialGet organization on boardCapture app ideasMust be on board with chosen toolsSlide26
The First ProjectChoose for successAllow extra time for learning curvesIterate to get visibilityLook for data sources that are already REST-basedSpread the knowledgeSlide27
MEAP Defined “A Mobile Enterprise Application Platform is a development framework that provides tools and client/server middleware for mobile applications.”Slide28
MEAP ToolsVendors support to varying degreesFeatures:MiddlewareScripting Language for phoneDevice managementApp ManagementPhone clientPrivate app storeNot cheapSlide29
MEAP Costs
Phone Client per device/per app and sometimes per month
Servers may be your site or theirs
Tools
Phone client
Middleware
App store
Development tools (IDE and/or Language)
App/Device ManagementSlide30
Vendors
Rhomobile –
www.rhomobile.com
Antenna Software –
www.antennasoftware.com
Kony Solutions –
www.kony.com
Apperian –
www.apperian.com
Mobile Iron – www.mobileiron.com
JAMF Casper – www.jamfsoftware.com
Mobiquity – http://mobiquityinc.comSybase – www.sybase.comSlide31
Summary
Approach from an Enterprise point of view
Mobile Enterprise Apps are universal across disciplines
Have a mobile computing plan
Identify an evangelist
Treat mobile apps as systems, not just “phone programs”Slide32
Contact Info
Norman Smith
SAIC
Technical Fellow
Assistant VP For Technology
smithno@saic.com
865-481-2990