3. Getting to Here
Growth in device market
Mobile was a peripheral, but becoming an essential
Making the experience
New tech, new ideas
Tweet: #SCON12
4. Getting to There
2010
Sugar Mobile
• Built on Titanium 2012 -
• Connected mode only
• iPhone and Android
• Simple administration
Project Nomad
2011 • Replacement for previous
solutions, but leverages best
concepts from both of them
Sugar Mobile • Developed internally
• iPhone, Android
Plus • One UX across all devices
• Simple but robust
administration
• Built on iEnterprises
• Offline mode
• iPhone and Blackberry
• Complex administration
Tweet: #SCON12
5. Joint Technology – Mobile
Technology & Dependencies
Technology
HTML5, Javascript:
backbone.js, bootstrap, Phon
egap
Authentication:
Oauth (v2)
LDAP
becomes
Depends On
New REST API being
developed for the Sugar 6.6
release
Removes need for a separate
sync server component
Tweet: #SCON12
6. Joint Technology – Mobile
Devices & Delivery
Devices:
Phase 1: Apple iOS 5.1 or greater (includes
iPhone 4)
Phase 2: Android 2.3 or greater
Mobile web browser compatibility
Delivery:
Apple App Store
Android Market
Direct download: SugarCRM.com
Amazon Appstore (Android)
Tweet: #SCON12
7. What will Mobile look like?
Coherent UX
Sugar-driven layout
Support the user with functionality
Scalability
Social CRM
Tweet: #SCON12
8. Mobile UX
Content subject to change. Please feel free to provide feedback.
Tweet: #SCON12
9. Call Flow
Start at a Record Detail View Phone# Selection Call In Progress to Call
Tweet: #SCON12
Growth in smart phone & tablet sales is already remarkable yet still gaining momentumMobile was a peripheral, but becoming an essential It’s not about recreating all features in a smaller form factor, but making a complimentary experienceNew open technologies are causing convergence of social networking, mobility and CRM into a real experience that feels more intuitive and a logical progression
* that’s coherent and consistent across multiple devices* A UX that is has an overall design that can be coherent and consistent across multiple devices, and complimentary to the core app. A natural extension of the core app experience* Layouts metadata driven via Studio; no need for extra configuration at middleware layer, support custom fieldsClean activation process for multiple devices per usersupport functionality that helps the user succeed, not bombard them with flash* I18n (internationalization) – proper language support* Enterprise scalability; the experience should work as well at 10,000 users as it does at 10.* Social integration