Challenges in adopting_mobility_v2
- 1. Challenges in adopting Mobility 2012
- 2. Challenges faced Data Security outside the corporate walls CXO ROI justification for additional investment CXO (Sr.Mgt.) How to Increase the reach ? (Sr.Mgt.) Fragmentation of mobile devices and operating platforms IT & Admin Trade off between Rich UI Vs wide Device IT & support Admin Data Integration between mobiles apps and ERPs Seamless Scalability Training of users on mobility End Users Flexibility and ease of use of the system. End Users Offline Access. Application responsiveness. Why should I use this ? Challenges faced by the stakeholders
- 3. How to approach Security CXO (Sr. Mgt.) • Storage Security (encrypted) Data Security outside the corporate walls • Transmission (SSL) ROI justification for additional investment • Firewall friendly (HTTP/S) Increasing Reach. • Complies with existing security policies • Data Encryption on device. ROI • Solution to run on at least 80% of existing devices • Is there a cloud offering • SAS / Managed Model Increasing Reach • Identifying devices with widest reach. • Some devices can never be supported.
- 4. How to approach Fragmentation • When to use HTML5 / Native • Choose a VM approach User Interface • Design multiple UI – platform specific IT & Admin (15%) • Keep the Business process - cross Fragmentation of mobile devices and platform (85%) operating platforms Trade off between Rich UI Vs Wide Integration device support • Take ‘middleware’ approach Data Integration between mobile apps • Use Parking Bays and Queues and ERPs • Insulate changes on either sides Seamless Scalability Training of users on mobility Seamless Scalability • Going from Pilot to Production (MDM) • Server Load balancing, Failover etc Training • Keep it Short/Simple & part of the apps • Circulate updated how-to’s part of the app
- 5. How to approach Ease of use • Give importance to UI richness (iPhone Vs J2ME) Offline Access • Offline systems are key • For real-time transactions opt for hybrid systems • Application Responsiveness • Quick to Start and finish Txns. • Should not add complexity to existing processes. Why Should I use this ? • It is psychological (Am I Being End users Tracked ?) • Accept users feedback in the design Flexibility and ease of use of the system and usage models. Offline Access • Elevates User’s status and Application responsiveness satisfaction. Why Should I use this ? • Impress upon them that this will Reduce their workload
- 6. Thank You www.godbtech.com sales@godbtech.com (+91) (44) 43 99 77 00
- 7. About Us 12 year old company based in Chennai 400 man years of Enterprise mobility experience Alliance network of 100 plus partners worldwide 150 plus customers (12 Fortune 500 relationships) Over 70,000 active deployments Cumulative of 200m transactions/year Deloitte Fastest 50 growing Company Microsoft India’s Emerging in India (2007, 2008) Innovative Company from India (2007)