1. Designing Enterprise Mobile Applications
Critical Success Factors
August 29, 2012

2. About Perficient
Perficient is a leading information technology consulting firm serving clients
throughout North America.
We help clients implement business-driven technology solutions that integrate
business processes, improve worker productivity, increase customer loyalty and create
a more agile enterprise to better respond to new business opportunities.

3. Perficient Profile
 Founded in 1997
 Public, NASDAQ: PRFT
 2011 Revenue of $260 million
 Major market locations throughout North America
— Atlanta, Austin, Charlotte, Chicago, Cincinnati, Cleveland,
Columbus, Dallas, Denver, Detroit, Fairfax, Houston,
Indianapolis, Los Angeles, Minneapolis, New Orleans,
Philadelphia, San Francisco, San Jose, Southern California,
St. Louis and Toronto
 Global delivery centers in China, Europe and India
 2,000+ colleagues
 Dedicated solution practices
 87% repeat business rate
 Alliance partnerships with major technology vendors
 Multiple vendor/industry technology and growth awards

4. Our Solutions Expertise & Services
Business-Driven Solutions Perficient Services
• Enterprise Portals  End-to-End Solution Delivery
• SOA and Business Process Mgmt  IT Strategic Consulting
• Business Intelligence  IT Architecture Planning
• User-Centered Custom Applications  Business Process & Workflow
• Interactive Design Consulting
• CRM Solutions  Usability and UI Consulting
• Enterprise Performance Management  Custom Application Development
• Customer Self-Service  Offshore Development
• eCommerce & Product Information  Package Selection, Implementation
Management and Integration
• Enterprise Content Management  Architecture & Application Migrations
• Enterprise Resource Planning  Education
• Management Consulting  Interactive Design
• Industry-Specific Solutions
• Mobile Technology Perficient brings deep solutions expertise and offers a
complete set of flexible services to help clients
• Security Assessments implement business-driven IT solutions

5. Our Speakers
Eric Roch
• Chief Technologist for Perficient
• 20+ years of experience in various aspects of
Information Technology including:
• IT executive level management within industry and
consulting
• technical architecture
• application and systems development.
• He has also been an IT industry speaker and
author for many years.
Kevin Orbaker
• Director, SOA/Integration at Perficient
• 20+ years of experience in various aspects of
Information Technology.
• Software Solutions Architect
• Enterprise Infrastructure Architect
• Executive Management
• Industry speaker and recognized community
contirbutor

6. Perficient’s Mobility Practice
6

7. Agenda
• About Perficient
• Perficient’s Mobility Practice
• Mobility Experience Design
• Mobility Enterprise Architecture
• Mobility Application Development
– Process lifecycle
– Solution Architecture
– Standards and Frameworks
• Perficient’s Mobility Roadmap
• Case Studies
7

8. Perficient Mobility Solution Offerings
Perficient’s mobility practice provides expertise across a variety of
enterprise platforms and technologies. Our approach is device
independent and scalable for emerging technology.
• Business Case Definition
• Vision and Roadmaps
• Experience Design
• Architecture and Frameworks
• Custom Development
• Back Office Integration
8

9. User Experience Design
9

10. Responsive Design
Responsive websites
adapt (and respond) to
their environment.
Same site, different
experiences.
10

11. Responsive Design
11

12. Responsive Design
V
S
12

13. Mobile Architecture
13

14. Architecture Constraints
• Limited: battery life, bandwidth,
memory, storage
• Large data sets: paging, parsing,
filtering
• Support native runtime features
(graphics, camera, GPS)
• Rich user experience over slow data
connections
• Connectionless environments
• Security and transactional state
regardless of connection
• Context awareness and digital memory
• All-ways-on: Agents, events and rules,
RFID, sensors and actuators
Pervasive computing is coming. How will your architecture
support it?
14

15. Mobile Architecture Concerns
Bolt on point- Layered
to-point Extensible
Service-Oriented
Value in reusable services and architecture consistency
15

16. Architecture Goals
Intuitive
Rapid
Change
Manage
APIs and
Developer
Community
Leverage
SOA,
Integration
Patterns,
Security
Complex
Slow to
Change
Layered architecture leveraging existing IT assets and
cloud integration 16

17. Mobile Enterprise Architecture Landscape
17

18. Mobile Architecture Decision Points
Mobile Browser Single Device Custom code
OR OR OR
Native App? Multiple Devices? Platform?
18

19. Mobile Enterprise Application Platforms
On-premise Systems SaaS/Cloud Systems Public Services
• A MEAP is a central mobile
MEAP development platform
Application Server
• The leading MEAP solutions allow
you to develop a single application
and seamlessly deploy it to multiple
providers (Apple, Android,
Blackberry) and multiple device
types (tablets, SmartPhones)
• Most MEAPs have pre-built
• iOS connectors to many common data
• Android sources (ERP, CRM, DW)
• Blackberry
• Windows Mobile
19

20. Gateway Proxy – Security and Protocol Mediation
20

21. RESTful APIs for Mobile
• Consistent and intuitive API
design
• Published, reusable APIs
• Leverage SOA investments
• API governance and ownership
• Developer community portal
• Protocol mediation – Web
Services to REST/JSON
• Security handshakes
• API monitoring
• API traffic throttling
21

22. Mobile Application Development
22

23. Agile Meets User Expectations for Rapid Iterations
Practices …that promote Collaboration
with Business
• Release Planning
• User Stories
Manageability
• Iteration Planning Visibility
• Daily Standup Meetings
• Test Driven Development Iterative Scope
• Unit Testing Stakeholder Feedback Control
• Continuous Integration Visibility Loop
• Refactoring
• Iteration Metrics
• Customer Show and Tell Predictability
Adaptability
Continuous
Improvement
23

24. Our Agile Approach to Mobility
Plan Develop Deploy
• Mobile Needs Assessment • User Stories • Test
• Mobile Vision and Strategy • Release Planning • App Signing
• Device Selection • Iteration Planning • App Certification
• Device Capabilities List • Task Breakdown • App Provision
• On-Board Storage Assessment • Daily Standup Meetings • Updates / Fixes
• Disconnected Usage Scenarios • Test Driven Development • Device Migration / Sunset
• Services and Data Assessment • Unit Testing
• Data Transfer Mechanisms • Continuous Integration
• Device Security Policies • Refactoring
• App Provisioning Strategy • Iteration Metrics
24
• Customer Show and Tell

25. Native Mobile Application Development
25

26. Native Apps Direct Access to OS APIs
26

27. Web Based Development with Limited OS APIs
27

28. Hybrid Mobile Application Development
28

29. Application Architecture Standards
• API naming standards
• Data format standards
• Library standards
• Hybrid frameworks
• Native frameworks
• Cross-platform
frameworks
• Solution architecture
patterns
• Design standards
• Coding standards
• Packaging standards
• Continuous integration
• Testing frameworks
• Deployment standards and
automation
29

30. Application Architecture Frameworks
• Architecture Patterns
• OOA/OOD
• Class Libraries
• Reusable elements
• Web views
• Table views and scrolling
• HTTP services
• Security
• Data persistence
• Disconnected operations
• Error handling, Logging
and debugging
30

31. Mobility Roadmap
31

32. Perficient’s Mobility Roadmap
Perficient’s mobility roadmap defines mobility efforts in the context of
a program that meets business goals. The roadmap will also defined
activities needed to create a consistent user experience,
comprehensive architecture and standardized application development
practices.
The roadmap will include activities to
addressing the following needs:
• Business vision and goals
• User experience and branding
• Application integration architecture
• Development approach and lifecycle
• Organizational suture and governance needs
• Development tools and framework needs
• Define Quick-win Pilot Project
• Program timeline, budget, iterations
32

33. Mobility Application Roadmap
Business goals for mobility drive the mobile application portfolio
development and the requirements for the portfolio drive architecture
decisions.
• Define each mobile application based on business goals
• Understand components needed for each mobile application
• Learn the audience and key scenarios where mobile applications will be
used
• Define the design considerations for mobile applications – user
experience and architecture requirements
• Identify specific scenarios for mobile applications, such as security,
deployment, power usage, integration and synchronization
• Define the key patterns and technology considerations for designing
mobile applications
• Determine high-level project estimates, timelines, and benefits
• Develop program roadmap and architecture vision to support the to-be
mobile portfolio
33

34. Mobility Roadmap Deliverables
While each of our customers needs are unique and as such our roadmaps are
customized the following deliverables a typical for mobile roadmaps:
• Documented business goals and critical success factors
• Recommended organizational model and governance frameworks
• Platform architecture recommendations and implementation timelines
• Experience design strategy
• High-level as-is and to-be architecture to support mobile
• Experience design, architecture and development of a pilot mobile
application
• Plans to mature people, processes and technology driven by business
needs and project requirements
• Candidate mobile applications with high-level costs and benefits; typical
mobile candidate projects include:
• Marketing and customer loyalty
• Customer and employee self service
• Content distribution – knowledge management, marketing, process documentation
• Business process tasks notifications and approvals
• Work order and field service automation
• Inventory management
• Logistics optimization
• Messaging and alert notification
34

35. Sample Roadmap
35

36. Mobility Roadmap Timelines and Staffing
The investment in a mobile roadmap varies with the detail of candidate
application discovery and estimation; the complexity of pilot project and the
implementation of mobile platforms to support the pilot. Roadmaps,
architecture, frameworks and organization skills are developed over time and
the roadmap is a living document and ongoing process.
The following are options for the development of the mobility roadmap:
• Mobility current-state assessment and recommended action items
• 2 Weeks
• XD Architect and Mobility Architect
• Mobility roadmap and pilot project
• 3-5 Weeks
• XD Architect, Mobility Architect, Mobile Developer
• Mobility Standards, Architecture and Frameworks
• 5-6 Weeks
• XD Architect, Mobility Architect
• If done with a pilot project add Mobile Developer
36

37. Case Studies
37

38. Progress Energy
Experience Design
Perficient designed and developed a cross-platform experience for Progress
Energy that included a new web site redesign, the conversion of traditional
offline communications to an interactive iPad application and the creation of a
customer mobile application optimized for iPhone and Android devices, while
providing alternate experience for basic mobile browsers.
38

39. PetSmart
• PetSmart, Inc. provides products, services, and
solutions for the lifetime needs of pets across
North America.
• Enterprise Service Bus (ESB) Product Selection
• SOA Readiness - Business Case and Technology
selection.
• Established the SOA Competency Center
• Created SOA Standards
• Developed the SOA Project Roadmap
• Implementation of "The Information Bus" project
– Implemented a real-time, event driven ESB
• Implementation of project "ASTRO" - real-time
integration among enterprise applications
• Sales Process Enhancement Project - real-time
POS data
• Implementation of Demand Planning Integration
• Establishment of PetSmart’s B2B gateway
• Design and development of Carrier Notifications -
improve freight visibility
• Enabled PetSmart vision for a mufti-channel
strategy
39