Abhijit SurPrincipal Solution ArchitectNov 2011
Mobile Applications            1        Defining a Service Platform                  Enterprise Applications        2     ...
Enterprise       Mashup       ConsumerConsumer                          Apps            Apps          Apps                ...
Demand for                                     Shifting Business              Predictive                                  ...
Abstraction of                                                     capabilities                   UI/UX                   ...
Adaptive behavior     • App Behavior should adapt based on     Context                          underlying network access ...
How can app developers design an app to leveragecapabilities of underlying network?              Design applications to be...
Sample Enterprise         Design Feature              Guiding Architecture Application                                    ...
Knowledge                                        Business     Development                          Sharing,           Inno...
What are the collaboration requirements                      How can a Collaboration Platform meetEnterprise Collaboration...
Enterprise Mobile Applications   Trends And Perspectives
Upcoming SlideShare
Loading in …5
×

Enterprise Mobile Applications Trends And Perspectives

884 views

Published on

Disclaimer: Views presented in this deck are exclusively my thoughts on the subject. They don't represent views of any of my past/present clients, employers and business associates.

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
884
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Enterprise Mobile Applications Trends And Perspectives

  1. 1. Abhijit SurPrincipal Solution ArchitectNov 2011
  2. 2. Mobile Applications 1 Defining a Service Platform Enterprise Applications 2 Impact of Mobility Mobile Enterprise Applications 3 Need for Context Awareness, Architecture Guiding Principles Enterprise Collaboration – A Mobility Use Case4 Requirements of an MEAP to support Enterprise Collaboration
  3. 3. Enterprise Mashup ConsumerConsumer Apps Apps Apps Service ExposureExecution Service OrchestrationEnvironment -CommunicationService Service Service Execution ServiceProvider, Creation MGMTEnterprise and Service EnablersMEAP Provider Network Abstraction LayerEnterprise Resources Enterprise 2G/3Gand Network Access IMS/LTE PSTN Resources Wireless
  4. 4. Demand for Shifting Business Predictive & Consumption Multi Core Analytics1 for Models – Systems enabling business Multiple devices multiple threads processes and in Multiple of execution consumer Environments applications Trends and Enablers shaping Enterprise MobilitySource: Gartner Report (Sep 2011).
  5. 5. Abstraction of capabilities UI/UX Loose Coupling of services Enterprise Service Data Discoverability Enterprise Services and Service Business Reusability and Processes ComposabilityNew usage patterns fostered by Mobility require changes in interactionsbetween key components of service design for enterprise apps
  6. 6. Adaptive behavior • App Behavior should adapt based on Context underlying network access layer of mobile device Aware • Adaptive app behavior based on apps location and presence Service Platform to support Management of • Branded User Context • Middleware to manage multiple creation, multiple user user contexts (enterprise/personal delivery, contexts use) execution and • Support enforcement of subscriber, management Policy Management service and corporate policies to define Quality of of mobile • Employ policy and not policing for applications Experience improved QoE.Mobile Enterprise Applications should aim for higher Quality ofExperience and not just providing ubiquitous access to enterprise data.
  7. 7. How can app developers design an app to leveragecapabilities of underlying network? Design applications to be adaptive for multiple access networks – 2G, 3G, 4G, Wi-Fi Pre-Fetch for faster user experience when underlying network is 4G/Wi-Fi * Employ bigger buffers and frequent caching – when applicable (being mindful of network spikes) * Fewer requests over network (grouping requests in one session) – when applicable * Adapt behavior based on customer’s rate plan (e.g. is it unlimited rate plan) and usage context.Mobile applications can no longer be “One Size Fits All”* Source: Marko Gargenta (2011)
  8. 8. Sample Enterprise Design Feature Guiding Architecture Application /Design Principle Insurance App to Task is available to user Design loosely coupled and approve commission to within 3 screen (at most) autonomous enterprise services so insurance agent navigation (Break an that they can be abstracted for app enterprise process into consumption smaller sub-processes) Healthcare – Access to Employ a media aware Mediation, Transformation and Patient Data service bus for managing Routing of digital media to be media (patient data) treated separately from messages transformation workflow in an ESB. Self Service Enterprise Employ a pull model for Solution should be network aware App to reload previous updates rather than and request for updates (say) only apps after a device forcing push updates by when the underlying network is enterprise 4G/Wi-Fi and not when it is a change congested 3G networkDesigning an enterprise mobile application need to consider UI/UX andavailability of enterprise data in offline/online mode (as required).
  9. 9. Knowledge Business Development Sharing, Innovation Process of Syndication & Efficiency Communities Management Collaboration Objectives can be overlappingA Mobile Enterprise Application Platform (MEAP) can be leveraged tosupport enterprise collaboration
  10. 10. What are the collaboration requirements How can a Collaboration Platform meetEnterprise Collaboration Platform from an Enterprise Ecosystem? the need  Capability to support multi device and multi 1  Collaboration solution should provide a platform that data formats for collaboration supports multiple devices and data formats  Support real-time and non-real time  Collaboration platform should provide tools and (asynchronous) collaboration 2 technologies to support both forms  Capability to contextualize collaboration based  Collaboration platform should be able to capture the on the requirements and user preferences 3 context and adapt the experience based on it.  Capability to support multi level participation  Collaboration platform should support any degree of style for collaboration 4 participation – open to closed levels.  Support different modes of collaboration  Collaboration platform should be able to support both governance model 5 flat and hierarchical form of governing structure  Support multi pronged incentive model for  Collaboration platform should support revenue sharing collaboration (financial and non financial) 6 models and non-monetary incentives, such as higher visibility, higher “ranking” within peer group  Serve the Long Tail of collaboration users 7  Expose collaboration capabilities as services that can be wired into Enterprise Mashups  Capability to capture KPIs for the collaboration  Collaboration platform should be integrated with services and applications 8 Business Intelligence, Data Management and Reporting systems of an enterprise

×