We want to stress the depth of our experience. We not only build mobile apps, we build them with the proper business strategy, experience design, architecture and development approach.
We can define the enterprise strategy and roadmap (steps to achieve strategy), the user experience design and brand strategy, enterprise architecture to support mobile including SOA, integration, security, and mobile device management. Our mobile development practices includes an agile approach, development standards and frameworks.
The user experience is key to success
The brand strategy and experience design is established across all form factors. ED is the application of user-centered design practices to generate cohesive, predictive and desirable designs based on holistic consideration of users’ experience.
Visual DesignVisual design, also commonly known as graphic design, communication design or visual communication, represents the aesthetics or “look-and-feel” of the front end of any User Interface. Graphic treatment of interface elements, such as the “look” in the term look-and-feel is often perceived as the visual design. The purpose of visual design is to use visual elements like colors, images, typography and symbols to convey a message to its audience. Fundamentals of Visual Perception give cognitive perspective on how to create effective visual communication.Information ArchitectureInformation architecture is the art and science of structuring and organizing the information in products and services, supporting usability and findability. More basic concepts that are attached with information architecture are described below.
Users perception of your mobile application is a reflection of your brand. Poor design impacts usability, customer retention and productivity.
Too many companies are building mobile application as one-off, bolt-on applications with inconsistent architecture. This will prove to be difficult to maintain and may cause problems such as poor performance, availability issues and security risks.
There are special considerations for mobile development that should be handled using a consistent architecture.
Bolting on many mobile applications will lead to a brittle architecture that will become difficult to change and expensive to maintain.
An architecture is needed that is responsive to rapid change and supports enterprise architecture concerns such as security and availability while leveraging investments in SOA
The architecture should support a development ecosystem – e.g. external developers and partners using your APIs
Platforms, standards and software are evolving and the decision points are critical
MEAPs are new technologies and are quite a bit different from each other. There is also overlap in capabilities with technology found in SOA. Product requirements, selection and architecture roles should be considered.
A gateway product can support security and protocol mediation for multi-channel. Multichannel retailing is the merging of retail operations in such a manner that enables the transacting of a customer via many connected channels. Channels include: retail stores, online stores, mobile stores, mobile app stores, telephone sales and any other method of transacting with a customer. Transacting incudes browsing, buying, returning as well as pre and post sale service.Multichannel retailing is often said to be dictated by systems and processes when in fact it is the customer that dictates the route they take to transact. Systems and processes within retail simply facilitate the customer journey to transact and be served. Pioneers of multichannel retailing include Macy's, Next PLC, John Lewis and Neiman Marcus. The pioneers of multichannel retail built their businesses from a customer centric perspective and served the customer via many channels long before the term 'multichannel' was used. Recent variations of the term include omni-channel.
Mobile and social needs Application Program Interfaces (API) to access enterprise information and perform tasks. API need to be properly designed, managed and supported by the enterprise architecture.
The section covers the approach to mobile application development. An Agile (fast) development methodology, development standards and reusable frameworks.
Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.
There are unique aspects to developing mobile applications that we incorporate into our Agile approach to mobility.
Native applications leverage the full power of the device and may be needed for the optimal user experience. When developing many applications this will be an expensive approach.
Native applications have full and direct access to the mobile OS APIs
Web based applications have more limited access to the OS APIs. However, web developer skills can be leveraged and HTML5 is improving.
Hybrid apps can leverage HTML and use APIs where needed
Application architecture standards are needed to improve productivity, create consistent designs and applications.
Reusable frameworks improve productivity and create consistent architecture
The roadmap aligns business goals, people, processes and technology
Driven by business goals and ROI. Matures people, processes and technology along a timeline.
Creates detailed plans based on business goals including costs, benefits and ROI
Combines strategy, project timelines and costs, organization and people, architecture and technology
Mature people, process and technology in the context of projects that deliver business value
Common design across form factors
Enterprise architecture to support multi-channelincluding mobile
Designing Enterprise Mobile Applications: Critical Success Factors
Designing Enterprise Mobile Applications Critical Success Factors August 29, 2012
About PerficientPerficient is a leading information technology consulting firm serving clientsthroughout North America.We help clients implement business-driven technology solutions that integratebusiness processes, improve worker productivity, increase customer loyalty and createa more agile enterprise to better respond to new business opportunities.
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
Our Solutions Expertise & ServicesBusiness-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
Our SpeakersEric 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
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
Perficient Mobility Solution OfferingsPerficient’s mobility practice provides expertise across a variety ofenterprise platforms and technologies. Our approach is deviceindependent and scalable for emerging technology.• Business Case Definition• Vision and Roadmaps• Experience Design• Architecture and Frameworks• Custom Development• Back Office Integration 8
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 actuatorsPervasive computing is coming. How will your architecturesupport it? 14
Mobile Architecture ConcernsBolt on point- Layered to-point Extensible Service-Oriented Value in reusable services and architecture consistency 15
Architecture Goals Intuitive Rapid Change Manage APIs and Developer Community Leverage SOA, Integration Patterns, Security Complex Slow to ChangeLayered architecture leveraging existing IT assets andcloud integration 16
Mobile Architecture Decision PointsMobile Browser Single Device Custom code OR OR OR Native App? Multiple Devices? Platform? 18
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
Gateway Proxy – Security and Protocol Mediation 20
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
Perficient’s Mobility RoadmapPerficient’s mobility roadmap defines mobility efforts in the context ofa program that meets business goals. The roadmap will also definedactivities needed to create a consistent user experience,comprehensive architecture and standardized application developmentpractices.The roadmap will include activities toaddressing 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
Mobility Application RoadmapBusiness goals for mobility drive the mobile application portfoliodevelopment and the requirements for the portfolio drive architecturedecisions.• 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
Mobility Roadmap DeliverablesWhile each of our customers needs are unique and as such our roadmaps arecustomized 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
Mobility Roadmap Timelines and StaffingThe investment in a mobile roadmap varies with the detail of candidateapplication discovery and estimation; the complexity of pilot project and theimplementation of mobile platforms to support the pilot. Roadmaps,architecture, frameworks and organization skills are developed over time andthe 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
Progress EnergyExperience DesignPerficient designed and developed a cross-platform experience for ProgressEnergy that included a new web site redesign, the conversion of traditionaloffline communications to an interactive iPad application and the creation of acustomer mobile application optimized for iPhone and Android devices, whileproviding alternate experience for basic mobile browsers. 38
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