UX and Design: Top Tips for Salesforce Apps on Mobile and Wearables
3 likes1,045 views
With Salesforce1, all Salesforce apps automatically work on any mobile device. But with new form factors like smart watches and wearables, how should you approach UX and design? Doing an email approval on an Apple Watch is one thing, but what about drilling down on a Wave dashboard? Join us as we discuss what we learned with designing Salesforce apps for tablets, smart phones, and smart watches. We'll discuss which Salesforce use cases make the most sense for different types of devices, the impact of "glanceability," and how to chunk out information for different devices.
Ad
More Related Content
What's hot (20)
Viewers also liked (13)
Ad
Similar to UX and Design: Top Tips for Salesforce Apps on Mobile and Wearables (20)
Ad
More from Salesforce Developers (20)
Recently uploaded (20)
UX and Design: Top Tips for Salesforce Apps on Mobile and Wearables
- 1. UX and Design: Top Tips for Salesforce Apps on Mobile and Wearables Mitch Kreaden Director of Product Management
- 2. © 2015 Ap)us Corpora0on 2015 / Confiden0al Presenters Dominic Steil Sales Engineer Ap.us Mitch Kreaden Director of Product Management Ap.us Dan Reid Senior Director of Product Marke:ng DocuSign
- 3. • Safe harbor statement under the Private Securi0es Li0ga0on Reform Act of 1995: • This presenta0on may contain forward-‐looking statements that involve risks, uncertain0es, and assump0ons. If any such uncertain0es materialize or if any of the assump0ons proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-‐looking statements we make. All statements other than statements of historical fact could be deemed forward-‐looking, including any projec0ons of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future opera0ons, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. • The risks and uncertain0es referred to above include – but are not limited to – risks associated with developing and delivering new func0onality for our service, new products and services, our new business model, our past opera0ng losses, possible fluctua0ons in our opera0ng results and rate of growth, interrup0ons or delays in our Web hos0ng, breach of our security measures, the outcome of any li0ga0on, risks associated with completed and any possible mergers and acquisi0ons, the immature market in which we operate, our rela0vely limited opera0ng history, our ability to expand, retain, and mo0vate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-‐salesforce.com products, and u0liza0on and selling to larger enterprise customers. Further informa0on on poten0al factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-‐K for the most recent fiscal year and in our quarterly report on Form 10-‐Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings sec0on of the Investor Informa0on sec0on of our Web site. • Any unreleased services or features referenced in this or other presenta0ons, press releases or public statements are not currently available and may not be delivered on 0me or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obliga0on and does not intend to update these forward-‐looking statements. Safe Harbor
- 4. About ApAus Ap)us, the category-‐defining Quote-‐to-‐Cash soZware company, drives the vital business process between the buyer’s interest in a purchase and the realiza0on of revenue. Ap)us is delivered on the Salesforce1 plaorm. Our applica0ons include Configure Price Quote (CPQ), Renewals, Contract Management and Revenue Management. Ap)us serves over 70 Fortune 500 customers and hundreds of mid-‐size companies. Learn more: ap.us.com
- 5. • How should you approach UX and design • Choosing use cases that make the most sense • Mobile and Wearable App Demos • Grouping informa0on & the Impact of glance-‐ability • Lightning Demo • Lessons learned designing Salesforce apps Focus Points
- 6. • Smartphone sales surpass PC sales since 2012 • People touch their phone up to 150 0mes a day • Mobile internet now exceeds desktop internet usage • 1.2 m apps were developed for iPhone and Android Ø Up to 87% of mobile apps are deleted within six months • Wearables will grow from 19.6 m in 2014 to 126.1 m by 2019 Why Mobile and Wearables
- 8. 1. Know Your Audience • Designed for specific use cases in mind 2. Make it Easy to Access/Use • Simplified UI 3. Make it Cool & Familiar • Converge Mobile, Web & SFDC UX 4. Enable Users • Designed to increase produc0vity 5. Make it Reliable and Secure • Built on Salesforce1 Plaorm How to Approach Mobile Design
- 9. InnovaSon & SimplificaSon Usability User Adoption User Adoption
- 10. Choosing Your Use Case ApAus Quote-‐to-‐Cash Footprint BIG vs SMALL WIDE vs TALL CPQ Approval
- 11. ApAus CPQ Mobile Demo
- 12. Are You Ready For Wearables? • Grow from 19.6 m in 2014 to 126.1 m by 2019 • Adop0on rate parallels to tablets • Most successful wearables are smart watches and health/fitness trackers (i.e. 9 in 10 wearables) • Study: Increased employee produc0vity by 8.5% and job sa0sfac0on by 3.5% Source: IDC Worldwide Quarterly Wearable Device Tracker, March 30, 2015 Source: PWC
- 13. Differences between Mobile & Wearables • Extension of phone not replacement • Leverage WK and iOS posted standards • Keep goal simple & focused • Wearables is a revisit of early mobile days • Set realis0c expecta0ons • Time factors & space limits • iOS & SF Dev resources needed • Leverage Glances
- 14. ApAus Wearable Demo ApAus Approval Intelligence
- 15. Design Tips & Lessons Learned DO’S DONT’S • Set top 3 goals • Proper loca0on and size for tap targets • Focus on func0on first, then form • Speed & caching • Post customiza0on and usability tes0ng • Allow for mistake recovery • Complicate feature set • Forget that you are not the user • Forget state • Overcrowd views • Keep user wai0ng • Overuse push no0fica0ons • Go big in phase 1 Early mobile prototype
- 16. • h)ps://github.com/developerforce/SalesforceWear-‐DevPack-‐For-‐ AppleWatch • h)ps://developer.apple.com/watch/human-‐interface-‐guidelines/ specifica0ons/ • h)p://www.slideshare.net/search/slideshow? searchfrom=header&q=salesforce+mobile +2015&ud=any&Z=all&lang=**&sort= • h)ps://developer.salesforce.com/mobile/services/mobile-‐templates • h)p://www.slideshare.net/developerforce/visualforce-‐in-‐salesforce1-‐ op0mizing-‐your-‐user-‐interface-‐for-‐mobile Wearable Examples & Resources
- 17. DocuSign: Dan Reid, Sr. Director of Product Marke0ng
- 18. DocuSign Mobile Strategy • Free-‐to-‐Sign Growth Strategy (Mobile) – Need to serve a consumer and enterprise audience both • Na0ve Apps – Premium experience. Freemium with upsell – Tablet Apps • Mobile Web – Breadth coverage. Any device • SDK and Partners – Your partners sell for you • Salesforce Partnership – Key strategic alliances – SF1 Full FuncSonality NaSve Apps Consumer Features Enterprise CapabiliSes iOS Windows Phone Android HTML5 Salesforce1
- 20. Across Mobile Platforms 20% 26% iPad iPhone Android Win Phone/8 29% 5% DocuSign Consumer Accounts (by OriginaSon Channel)
- 21. Great Customer Experience Comes First – Native Apps § Sign and Send Documents § Customizable Workflow § Sign In-‐Person or Remote § Work in Offline Mode § Push No0fica0ons § Navigate Direct to Document for Signature § Manage and Filter All Documents in your Queue § Access Documents Directly from Salesforce
- 22. Salesforce1 § Integrated with Salesforce 1 § Specify Documents, Signers, and Workflow § Post Updates to Cha)er Automa0cally
- 23. Lightning
- 24. • Lightning framework • New UI layer for Salesforce • Consist of App builder, Components, exchange & design system • Lightning Design System (SLDS) • Collec0on of design pa)erns, components, and guidelines for crea0ng unified UI in the Salesforce ecosystem • Pure CSS framework to use with VF, lightning What Is App Builder & Lightning Components
- 25. • New tools to help Admins • Build apps (via App Builder) • Automate business processes (via App Builder) • Integrate data (via components) • Apps are comprised of components • Components can be created or consumed • Lightning uses an event driven framework/ Arch What Is App Builder & Lightning Components
- 26. Why Lightning MaAers • Trend towards component frameworks (Google=Polymer) • Help unify UX across ISV Apps • Provide design system & resources to leverage • New easy design tool for Dev teams AND Admins • Leverage components across large product footprints • Lightning is device aware (responsive design) • Minimize loading 0me for faster UX
- 28. Final Things To Think About • Style & Nav Consistency • App context (Russian Doll) • Needed (Wearable) & doable • Right delivery : S1, VF vs Angular, Lightning , na0ve App…… • Prototypes (www.invisionapp.com, )p://www.axure.com/) • Test using real data • Leverage exis0ng pieces (Wave, Lightning exchange, Lightning)
- 29. Q & A
- 30. Later today… 3 -‐ 3:20pm Build Apps Fast with Lightning Components from ApAus San Francisco Marrio. Marquis Hotel, Foothill E
- 31. Thank You & …..
- 32. Share Your Feedback, and Win a GoPro! 3 Earn a GoPro prize entry for each completed surveyTap the bell to take a survey2Enroll in a session1
- 33. Message & data rates apply. Visit h)p://bit.ly/TextAPT for T&C. — GET THE — UlSmate Guide to Quote-‐to-‐Cash Plus a chance for prizes including a GoPro or a Ricoh Theta 360 Camera. Text CASH to 95577
- 34. Presentation Title Goes Here Presenter Name / Date Built on the Salesforce1™ Plaform Quote Contract Revenue Opportunity ERP CONTRACT LIFECYCLE MANAGEMENT ORDER MANAGEMENT CONFIGURE PRICE QUOTE BILLING REBATE MANAGEMENT DEAL MANAGEMENT E-‐COMMERCE QUOTE-‐TO-‐CASH INTELLIGENCE X-‐AUTHOR ApAus Quote-‐to-‐Cash Footprint
- 35. • Mobile First -‐ Numerous devices • Casual users vs power users • Complex vs simple use cases • OTB vs configurable • SFDC UI vs new App UI • Micro moments & deep info access Approaching UX As A Salesforce Partner
- 36. © 2015 Ap)us Corpora0on 2015 / Confiden0al ApAus CPQ Mobile
- 37. © 2015 Ap)us Corpora0on 2015 / Confiden0al ApAus Approvals Intelligence
- 38. © 2015 Ap)us Corpora0on 2015 / Confiden0al ApAus Approvals Intelligence
- 39. © 2015 Ap)us Corpora0on 2015 / Confiden0al Lightning
- 40. © 2015 Ap)us Corpora0on 2015 / Confiden0al Lightning
- 41. © 2015 Ap)us Corpora0on 2015 / Confiden0al Lightning
- 42. © 2015 Ap)us Corpora0on 2015 / Confiden0al Lightning
- 43. © 2015 Ap)us Corpora0on 2015 / Confiden0al Lightning
- 44. © 2015 Ap)us Corpora0on 2015 / Confiden0al Lightning Component Exchange
- 45. © 2015 Ap)us Corpora0on 2015 / Confiden0al Lightning Design System
- 46. © 2015 Ap)us Corpora0on 2015 / Confiden0al ApAus QTC Mobile