Slide 1

Slide 1 text

#designsystem IXDA SF 10.14.2015 Lightning
 Design System @JINA SENIOR DESIGNER, DESIGN SYSTEMS

Slide 2

Slide 2 text

Safe Harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions 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 projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, 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 uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential 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 section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time 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 obligation and does not intend to update these forward-looking statements. #designsystem

Slide 3

Slide 3 text

user experience #designsystem

Slide 4

Slide 4 text

#designsystem @jina SENIOR DESIGNER, DESIGN SYSTEMS SALESFORCE

Slide 5

Slide 5 text

#designsystem “It used to be that designers made an object and walked away. Today the emphasis must shift to designing the entire
 life cycle.” — PAUL SAFFO

Slide 6

Slide 6 text

#designsystem Product design in an enterprise organization can be tricky!

Slide 7

Slide 7 text

#designsystem Salesforce1

Slide 8

Slide 8 text

#designsystem Design for Scale

Slide 9

Slide 9 text

#designsystem Support Multiple 
 Platforms & Devices

Slide 10

Slide 10 text

#designsystem Design for Configuration

Slide 11

Slide 11 text

#designsystem Dozens of Scrum Teams Hundreds of Developers Small Team of Designers

Slide 12

Slide 12 text

#designsystem Where can I find the icons? What color is the button border? Where can I find the icons?

Slide 13

Slide 13 text

#designsystem Redlines?

Slide 14

Slide 14 text

#designsystem

Slide 15

Slide 15 text

#designsystem Design Pages

Slide 16

Slide 16 text

#designsystem #FML

Slide 17

Slide 17 text

#designsystem Design Pages

Slide 18

Slide 18 text

#designsystem “A fractured process makes for a fractured user experience” — NATE FORTIN

Slide 19

Slide 19 text

#designsystem Design Systems

Slide 20

Slide 20 text

#designsystem Style Guides are all
 the rage …and they have come a long way

Slide 21

Slide 21 text

alistapart.com/article/writingainterfacestyleguide

Slide 22

Slide 22 text

#designsystem Brand & Design Standards Front-End Standards Keep your Style Guide Current & Useful

Slide 23

Slide 23 text

#designsystem Zombie Style Guides …are style guides that aren't maintained and part of your process.
 They die and rot. They eat your brains.

Slide 24

Slide 24 text

#designsystem It must be living

Slide 25

Slide 25 text

Ye Olde Salesforce1 Style Guide

Slide 26

Slide 26 text

#designsystem Last year at Dreamforce, we talked to developers about our Style Guide

Slide 27

Slide 27 text

#designsystem How do I get my app
 to look like this?

Slide 28

Slide 28 text

#designsystem Can I use the CSS
 in my app?

Slide 29

Slide 29 text

#designsystem Our partners & customers want their apps to look 
 like Salesforce

Slide 30

Slide 30 text

#designsystem They want our design language & best practices

Slide 31

Slide 31 text

#designsystem A 3rd-party Salesforce-ish Bootstrap-theme got distributed & used

Slide 32

Slide 32 text

#designsystem It was not maintained by us, so quickly grew out of sync with our UI updates

Slide 33

Slide 33 text

#designsystem Many partner apps look & work great, but don’t feel like Salesforce

Slide 34

Slide 34 text

#designsystem They needed better resources & tools

Slide 35

Slide 35 text

#designsystem They need to keep up with our design iterations

Slide 36

Slide 36 text

#designsystem Lightning Experience

Slide 37

Slide 37 text

#designsystem Have a clear vision to
 align efforts

Slide 38

Slide 38 text

#designsystem Our design principles are intentionally ordered by priority

Slide 39

Slide 39 text

#designsystem clarity Eliminate ambiguity. Enable people to see, understand, and act with confidence.

Slide 40

Slide 40 text

#designsystem efficiency Streamline and optimize workflows. Intelligently anticipate needs to help people work better, smarter, and faster.

Slide 41

Slide 41 text

#designsystem consistency Create familiarity and strengthen intuition by applying the same solution to the 
 same problem.

Slide 42

Slide 42 text

#designsystem beauty Demonstrate respect for people’s time 
 and attention through thoughtful and elegant craftsmanship.

Slide 43

Slide 43 text

#designsystem clarity > efficiency > consistency > beauty

Slide 44

Slide 44 text

#designsystem Do research &
 talk to your customers

Slide 45

Slide 45 text

#designsystem Keep testing as you go

Slide 46

Slide 46 text

#designsystem Accessibility is really freaking important

Slide 47

Slide 47 text

#designsystem A solution that works for us… & now for our customers, too

Slide 48

Slide 48 text

#designsystem Clarity

Slide 49

Slide 49 text

#designsystem Lightning Design System The next generation of living style guides

Slide 50

Slide 50 text

salesforce.com/designsystem

Slide 51

Slide 51 text

#designsystem Lightning Design System Guidelines and design patterns Consistent with the Salesforce UI Includes HTML, CSS, icons, and fonts Framework-agnostic Open Source

Slide 52

Slide 52 text

#designsystem Design Patterns

Slide 53

Slide 53 text

#designsystem Use plain language

Slide 54

Slide 54 text

#designsystem Keep your information architecture simple

Slide 55

Slide 55 text

#designsystem Don’t try to document & build everything at once

Slide 56

Slide 56 text

#designsystem Document & build
 going forward

Slide 57

Slide 57 text

#designsystem Efficiency

Slide 58

Slide 58 text

#designsystem “…Creating a positive experience is not about having best practices. It’s about putting those practices into the right hands.” — BRENDON CORNWELL

Slide 59

Slide 59 text

#designsystem Empower Developers Provide developers scalable & accessible code at beginning of 
 development cycle

Slide 60

Slide 60 text

#designsystem Empower Designers Design & iterate more efficiently in the browser

Slide 61

Slide 61 text

#designsystem Design System Components CSS Framework + UI Library

Slide 62

Slide 62 text

#designsystem Building an enterprise framework is tricky!

Slide 63

Slide 63 text

#designsystem Clarity > Brevity

Slide 64

Slide 64 text

#designsystem Namespaced classes with scoping option

Slide 65

Slide 65 text

#designsystem BEM
 (Block, Element, Modifier)

Slide 66

Slide 66 text

#designsystem .slds-button__icon--x-small

Slide 67

Slide 67 text

#designsystem .slds-button__icon--x-small NAMESPACE

Slide 68

Slide 68 text

#designsystem .slds-button__icon--x-small NAMESPACE BLOCK

Slide 69

Slide 69 text

#designsystem .slds-button__icon--x-small NAMESPACE BLOCK ELEMENT

Slide 70

Slide 70 text

#designsystem .slds-button__icon--x-small NAMESPACE BLOCK ELEMENT MODIFIER

Slide 71

Slide 71 text

#designsystem .slds-button__icon--x-small NAMESPACE BLOCK ELEMENT MODIFIER

Slide 72

Slide 72 text

#designsystem Objects/Components LIGHTWEIGHT MODULAR REUSABLE Dependencies DESIGN TOKENS Utilities NON-SEMANTIC SINGLE PURPOSE

Slide 73

Slide 73 text

#designsystem Living Style Guide + =

Slide 74

Slide 74 text

#designsystem Show the object with its states & variants

Slide 75

Slide 75 text

lightningdesignsystem.com/components/buttons

Slide 76

Slide 76 text

#designsystem Only show the code people need to see

Slide 77

Slide 77 text

#designsystem Don’t make it until you need it! (Be Lean)

Slide 78

Slide 78 text

#designsystem For our application, most typographic elements require spacing removed

Slide 79

Slide 79 text

#designsystem Since this is the most common case, we remove them by default

Slide 80

Slide 80 text

#designsystem Heading hierarchy levels vary depending on context & our customer’s needs

Slide 81

Slide 81 text

#designsystem Visual style & semantic hierarchy are not necessarily coupled

Slide 82

Slide 82 text

#designsystem Lists are used usually for their semantics, but rarely have bullets or margins

Slide 83

Slide 83 text

#designsystem We reset these styles &
 opt in with Utilities

Slide 84

Slide 84 text

#designsystem We use a scoped utility class to opt-back in on a parent-level

Slide 85

Slide 85 text

No content

Slide 86

Slide 86 text

#designsystem Clearer communication

Slide 87

Slide 87 text

#designsystem Designing in the browser

Slide 88

Slide 88 text

#designsystem Living specifications

Slide 89

Slide 89 text

#designsystem Better prototypes

Slide 90

Slide 90 text

#designsystem No more proliferation of inconsistent styles

Slide 91

Slide 91 text

#designsystem Consistency

Slide 92

Slide 92 text

#designsystem How do we keep colors, spacing, sizing, etc. consistent?

Slide 93

Slide 93 text

#designsystem How do we make future visual design
 changes faster?

Slide 94

Slide 94 text

#designsystem How do we keep 
 our design
 system agnostic?

Slide 95

Slide 95 text

#designsystem Single Source of Truth

Slide 96

Slide 96 text

#designsystem Assets are stored in repository and automatically updated in the app and style guide

Slide 97

Slide 97 text

#designsystem Design Tokens The basic atoms of the Design System

Slide 98

Slide 98 text

#designsystem Design Tokens help us scale design across both web & native applications.

Slide 99

Slide 99 text

#designsystem Some Types of Design Tokens Font Weights, Sizes, Families, & Line-Heights Colors for Background, Text, & Borders Shadows Spacing & Sizing Animation Durations Z-indexes Breakpoints

Slide 100

Slide 100 text

#designsystem Designers refer to
 Design Tokens in
 their specifications

Slide 101

Slide 101 text

#designsystem

Slide 102

Slide 102 text

#designsystem theo Open source tool by Salesforce UX to generate Design Tokens

Slide 103

Slide 103 text

#designsystem Theo JSON file converts to: Lightning Sass Less Stylus JSON (iOS) XML (Android) Style Guide Color Swatches (Photoshop & Sketch)

Slide 104

Slide 104 text

#designsystem THEO { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body text" } LIGHTNING SASS // Body text $color-text: #000;

Slide 105

Slide 105 text

#designsystem CSS — hex iOS — RGBA Android — 8-digit hex

Slide 106

Slide 106 text

#designsystem CSS — rem/em/px iOS — pt Android — sp/dip

Slide 107

Slide 107 text

Design Tokens

Slide 108

Slide 108 text

Design Tokens: Background Colors

Slide 109

Slide 109 text

Design Tokens: Font Sizes

Slide 110

Slide 110 text

Design Tokens: Radiuses

Slide 111

Slide 111 text

#designsystem Color Swatches

Slide 112

Slide 112 text

#designsystem No more
 hard-coded values

Slide 113

Slide 113 text

#designsystem Beauty

Slide 114

Slide 114 text

#designsystem Salesforce Sans ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789

Slide 115

Slide 115 text

#designsystem Base Unit of 4 for 
 spacing & sizing

Slide 116

Slide 116 text

#designsystem Modular, responsive
 type scale

Slide 117

Slide 117 text

#designsystem SVGs for crisp,
 scalable icons

Slide 118

Slide 118 text

#designsystem ENTER & EXIT EMPHASIS TRANSITIONAL PERSONALITY & BRANDING TIMING ELEVATION EFFECTS Motion Guidelines

Slide 119

Slide 119 text

#designsystem #A7B8D1 #CFD7E6 #EEF1F6 #4F6A92 #0070D2 #0C8EFF #00396B #005FB2 #EF7EAD #4BC076 #7F8DE1 #F88962 Color Palette

Slide 120

Slide 120 text

#designsystem Choose Your Design System Team Model

Slide 121

Slide 121 text

medium.com/eightshapes-llc/team-models-for-scaling-a-design-system-2cf9d03be6a0

Slide 122

Slide 122 text

#designsystem Team Model #1: Solitary A solitary model sees a one team make a system available, but with efforts focused primarily on that team’s needs VIA TEAM MODELS FOR SCALING A DESIGN SYSTEM BY NATHAN CURTIS

Slide 123

Slide 123 text

#designsystem Team Model #2: Centralized A single, central design team produces and supports a system used by others as a part of their job VIA TEAM MODELS FOR SCALING A DESIGN SYSTEM BY NATHAN CURTIS

Slide 124

Slide 124 text

#designsystem Team Model #3: Federated Designers from multiple 
 product teams decide on the system together VIA TEAM MODELS FOR SCALING A DESIGN SYSTEM BY NATHAN CURTIS

Slide 125

Slide 125 text

medium.com/salesforce-ux/the-salesforce-team-model-for-scaling-a-design-system-d89c2a2d404b

Slide 126

Slide 126 text

#designsystem A Cyclical Team Model Design System informs Product Design Product Design informs Design System

Slide 127

Slide 127 text

#designsystem Our centralized Design Systems team acts as a librarian, distributor, and facilitator, and we make sure it is maintained and crafted with quality.

Slide 128

Slide 128 text

#designsystem Our federated Design Systems contributors distributed throughout the organization keep the Design System accurate, current, and actually useful

Slide 129

Slide 129 text

#designsystem Bring designers, engineers, 
 & product managers together around a single goal

Slide 130

Slide 130 text

blog.capwatkins.com/the-sliding-scale-of-giving-a-fuck APOLOGIES FOR THE PROFANITY BUT IT’S A GREAT READ.

Slide 131

Slide 131 text

#designsystem Design Principles > Design Standards

Slide 132

Slide 132 text

#designsystem “Design considerations beat design patterns. Test and decide; don’t just copy things like the hamburger icon.” — JEFFREY ZELDMAN

Slide 133

Slide 133 text

#designsystem Resources

Slide 134

Slide 134 text

#designsystem salesforce.com/designsystem

Slide 135

Slide 135 text

#designsystem styleguides.io

Slide 136

Slide 136 text

#designsystem speakerdeck.com/jina/lightning-design-system

Slide 137

Slide 137 text

#designsystem @salesforceUX

Slide 138

Slide 138 text

#designsystem @jina

Slide 139

Slide 139 text

#designsystem “Be regular and orderly in your life so that you may be violent and original in your work.” — GUSTAVE FLAUBERT

Slide 140

Slide 140 text

#designsystem thank you! @jina