Slide 1

Slide 1 text

From zero to cosmos FRONT-END TEAM Cristiano Rastelli a journey to a multi-platform design system at Badoo

Slide 2

Slide 2 text

http://rosenfeldmedia.com/books/storymapping/

Slide 3

Slide 3 text

beginning evolution crisis enlightenment nirvana We are here

Slide 4

Slide 4 text

The full story • From zero to Cosmos — Part #1 / #2 / #3
 https://badootech.badoo.com/from-zero-to-cosmos-part-1-2d080fe35bf2
 https://badootech.badoo.com/from-zero-to-cosmos-part-2-97929e13f839
 https://badootech.badoo.com/from-zero-to-cosmos-part-3-95e2c98c45a6 • Systemantics — a review of the book
 https://medium.com/@didoo/systemantics-a778c4247cbb • How to manage your Design Tokens with Style Dictionary
 https://medium.com/@didoo/how-to-manage-your-design-tokens-with-style-dictionary-98c795b938aa • Generating multi-brand multi-platform icons with Sketch and a Node.js script —  Part #1 / #2
 https://badootech.badoo.com/generating-multi-brand-multi-platform-icons-with-sketch-and-a-node-js-script-part1-82f438c7e16c
 https://badootech.badoo.com/generating-multi-brand-multi-platform-icons-with-sketch-and-a-node-js-script-part2-8d02e8bb915a • Measuring the Impact of a Design System
 https://medium.com/@didoo/measuring-the-impact-of-a-design-system-7f925af090f7

Slide 5

Slide 5 text

Dramatis Personae

Slide 6

Slide 6 text

Cristiano Rastelli @areaweb FRONT-END TEAM @webdeldn

Slide 7

Slide 7 text

team.badoo.com

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

108 product 280 engineering 580 15 design 22 Front-end 50 ios / Android We’re hiring!

Slide 10

Slide 10 text

Under the radar where everything started

Slide 11

Slide 11 text

No components No atomic design

Slide 12

Slide 12 text

Global declarations

Slide 13

Slide 13 text

Copy&paste, no Modularisation

Slide 14

Slide 14 text

design handoffs

Slide 15

Slide 15 text

decision:
 we need a style guide

Slide 16

Slide 16 text

started small & lean working incrementally one component at a time
 with little overhead

Slide 17

Slide 17 text

Mobile Web style guide

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

Living Styleguide

Slide 20

Slide 20 text

Visual Regression Testing

Slide 21

Slide 21 text

diff AFTER before https://speakerdeck.com/nikhilverma/visual-regression-testing-from-a-tool-to-a-process

Slide 22

Slide 22 text

Deliver value* * business value, from day one

Slide 23

Slide 23 text

me, a pain in the ___ * * *

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

it gets noticed where I reaped the fruits of my labour

Slide 26

Slide 26 text

visible/tangible improvements • modularisation of components • reusability of code & components • speed of development • better visual consistency & overall quality

Slide 27

Slide 27 text

pitch to head of design for a shared component Library (between Mobile & desktop web)

Slide 28

Slide 28 text

The grand plan

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

the "re-think" project here come the dragons

Slide 33

Slide 33 text

BIGGER THAN DATING https://www.behance.net/gallery/55344175/New-Badoo-identity

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

2009 2013 2017

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

In theory the perfect use case for a style guide

Slide 41

Slide 41 text

In practice...

Slide 42

Slide 42 text

"There is no time !"

Slide 43

Slide 43 text

master RETHINK

Slide 44

Slide 44 text

the style guide was more and more in disarray, not maintained

Slide 45

Slide 45 text

components were broken or missing

Slide 46

Slide 46 text

VRT tests were broken

Slide 47

Slide 47 text

VRT tests were not added Rethink project

Slide 48

Slide 48 text

living Styleguide dead

Slide 49

Slide 49 text

it was a personal failure

Slide 50

Slide 50 text

I have not been able
 to communicate
 the value, the importance &
 the real potential of a style guide

Slide 51

Slide 51 text

Why keep it alive ?

Slide 52

Slide 52 text

not everything is lost where the “grand plan” takes place

Slide 53

Slide 53 text

https://medium.com/@didoo/systemantics-a778c4247cbb

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

"Failure to function as expected
 is an intrinsic feature
 of the systems".

Slide 56

Slide 56 text

a crucial email message

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

This is a designer telling (pushing) a front-end developer 
 to build a design system he didn't build a fence to protect
 his territory, he didn't say 
 "this is design, stay out of here !” He was understanding the value

Slide 60

Slide 60 text

a turning-point meeting “I want a Design System for all our mobile apps. 
 A style guide built together with the designers,
 based on the optimal / new / upcoming designs
 to serve as visual reference for the developers.” Sasha Grishin, Head of Design

Slide 61

Slide 61 text

decision:
 a design system for
 all our mobile apps*
 * desktop web is out (for now)

Slide 62

Slide 62 text

last year where things have taken off

Slide 63

Slide 63 text

finding a name

Slide 64

Slide 64 text

Space conquerors monument / Cosmonautics Museum in Moscow

Slide 65

Slide 65 text

Cosmos from Latinized form of Greek kosmos
 "order, good order, orderly arrangement" A complex orderly self-inclusive system,
 an orderly harmonious systematic universe.

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

the technical stack

Slide 69

Slide 69 text

design tokens { "button": { "border_radius": { "value": "{base.border_radius.value}", "type": "size" }, "border_width": { "value": “1px", "type": "size" } } }

Slide 70

Slide 70 text

https://amzn.github.io/style-dictionary/ Design decisions Tokens Data source docS system Tokens (JSON) Tokens (XML) VARIABLES (SASS) Tokens (PLIST) iOS Android web COSMOS VARIABLES (SASS) EMAIL

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

+

Slide 73

Slide 73 text

a great collaboration

Slide 74

Slide 74 text

team structure https://medium.com/eightshapes-llc/team-models-for-scaling-a-design-system-2cf9d03be6a0 solitary “federated” centralised

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

"We can't create an edge case for this" Pavel shumakov, Badoo designer

Slide 77

Slide 77 text

before Product Design Development QA

Slide 78

Slide 78 text

after Product Design Development QA Cosmos

Slide 79

Slide 79 text

Blocker (or bottleneck?) Product Design Development QA Cosmos

Slide 80

Slide 80 text

components breakdown

Slide 81

Slide 81 text

Cosmos celebration

Slide 82

Slide 82 text

the native apps
 & design teams

Slide 83

Slide 83 text

Badoo UI KIT & GALLERy

Slide 84

Slide 84 text

Badoo UI KIT & GALLERy

Slide 85

Slide 85 text

UI libraries in Sketch

Slide 86

Slide 86 text

Today where are we now?

Slide 87

Slide 87 text

show time !

Slide 88

Slide 88 text

http://cosmos/

Slide 89

Slide 89 text

No content

Slide 90

Slide 90 text

No content

Slide 91

Slide 91 text

No content

Slide 92

Slide 92 text

No content

Slide 93

Slide 93 text

No content

Slide 94

Slide 94 text

No content

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

No content

Slide 97

Slide 97 text

No content

Slide 98

Slide 98 text

No content

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

No content

Slide 101

Slide 101 text

No content

Slide 102

Slide 102 text

No content

Slide 103

Slide 103 text

No content

Slide 104

Slide 104 text

the human part

Slide 105

Slide 105 text

everyone can see only a small part

Slide 106

Slide 106 text

It's not in cosmos!!!

Slide 107

Slide 107 text

The real "story" “dragons” “dragons” “dragons”

Slide 108

Slide 108 text

The invisible
 human part
 of our daily jobs

Slide 109

Slide 109 text

This! this! This again & again! https://twitter.com/robinrendle/status/1113897759206072320

Slide 110

Slide 110 text

the "Atomic" problem

Slide 111

Slide 111 text

“Everything is a component.” Jina Anne, Nathan Curtis, Trent Walton, 
 Adam Morse, and many others

Slide 112

Slide 112 text

quark atom molecule organism layout other

Slide 113

Slide 113 text

flat Folders structure DESIGN TOKENS (JSON) UI COMPONENTS (React) STYLE GUIDE (React Web App)

Slide 114

Slide 114 text

we tend to have two distinct
 kind of components: pure layout & content decoration

Slide 115

Slide 115 text

“Layout” Composition “Content”

Slide 116

Slide 116 text

when in doubt, break down
 a component * Don't go “up” (using inheritance), or “sideways” (trying to cover too much)

Slide 117

Slide 117 text

The complexity is in the connections http://www.didoo.net/2015/07/modules-components-and-systems/

Slide 118

Slide 118 text

what metrics to use ?

Slide 119

Slide 119 text

Components Jul 2017 apr 2019 extrasmall 2 15 small 1 13 medium 2 10 large 1 5 extralarge 0 4 overall* 9 167 * components + subcomponents LOC - components/jsx 204 8075 LOC - components/SCSS 529 5851 LOC - WEBSITE/jsx 479 19294

Slide 120

Slide 120 text

Visual Regression Tests - Number of snapshots

Slide 121

Slide 121 text

The impact of Cosmos https://medium.com/@didoo/measuring-the-impact-of-a-design-system-7f925af090f7

Slide 122

Slide 122 text

git log --stat --reverse --date=short -- 'src/css/*.less' > ~/data-raw/logs_less.txt

Slide 123

Slide 123 text

No content

Slide 124

Slide 124 text

...And what about the users ? https://twitter.com/markdalgleish/status/1018760819104890880

Slide 125

Slide 125 text

looking forward what are the challenges we’re facing

Slide 126

Slide 126 text

how do you design a
 multi-product & multi-platform feature ?

Slide 127

Slide 127 text

What makes something
 "On-BranD" ?

Slide 128

Slide 128 text

The right balance BRAND IDENTITY COHERENCE REUSABILITY CONSISTENCY

Slide 129

Slide 129 text

how do we know
 that something "on-brand"
 is adding real value for the user ?

Slide 130

Slide 130 text

example: date of birth picker To continue you need to fill this forms D M D M Y Y Y Y D M D M Y Y Y Y 1 0 2 4 1 8 9 4 1 M D M Y Y Y Y Chappy Day Month Year 1 D M M Y Y Y Y Day Month Year D D M M Y Y Y Y Day Month Year 1 7 0 6 1 9 6 2 You must be over 55 to use Lumen 1 7 0 6 1 9 6 2 D D Day M M Month Y Y Y Y Year D D Day M M Month Y Y Y Y Year 1 D Day M M Month Y Y Y Y Year 1 4 Day 0 5 Month 1 9 9 3 Year 1 D You must be over 18 to use Badoo M M Y Y Y Y D D You can't be younger than 13 M D M Y Y Y Y 1 M 0 D 4 M 5 Y 1 Y 9 Y 9 Y 3 1 M D M Y Y Y Y Y D M Y M Y Y Day Month Year D Y D M Y M Y Y You must be over 18 to use Bumble D 2 7 0 1 6 9 2 Day Month Year 1 Y D M Y M Y Y Day Month Year 1 Bumble Badoo Quack Lumen

Slide 131

Slide 131 text

one design system, but...
 how many libraries ?

Slide 132

Slide 132 text

https://speakerdeck.com/yeseniaperezcruz/building-flexible-design-systems

Slide 133

Slide 133 text

how much of
 the User Interface
 should be covered?

Slide 134

Slide 134 text

" What can be reasonably left out " https://twitter.com/resmini/status/912373274323103751

Slide 135

Slide 135 text

conclusions lessons learned on this journey

Slide 136

Slide 136 text

it takes time to have buy in be patient (and don't give up!)

Slide 137

Slide 137 text

you can't push change you have to deliver value first

Slide 138

Slide 138 text

be prepared to fail because every system FAILs, it's its nature

Slide 139

Slide 139 text

learn from the others But then make your choices

Slide 140

Slide 140 text

A synthetic / approximate MEASURE IS BETTER T HAN NO MEASURE

Slide 141

Slide 141 text

"Nothing is particularly hard
 if you divide it in small jobs."
 Henry Ford Manifacturer

Slide 142

Slide 142 text

Thanks cristiano rastelli FRONT-END TEAM didoo . net / @areaweb