Slide 1

Slide 1 text

Flutter - A journey of productivity and happiness -

Slide 2

Slide 2 text

Once upon a time...

Slide 3

Slide 3 text

In 2016

Slide 4

Slide 4 text

What were we doing?

Slide 5

Slide 5 text

What were we doing? → Company iOS first (more resources, earlier releases)

Slide 6

Slide 6 text

What were we doing? → Company iOS first (more resources, earlier releases) → Client Java (and Kotlin later...)

Slide 7

Slide 7 text

What were we doing? → Company iOS first (more resources, earlier releases) → Client Java (and Kotlin later...) → Patterns MVVM (custom), Dagger 2...

Slide 8

Slide 8 text

What were we doing? → Company iOS first (more resources, earlier releases) → Client Java (and Kotlin later...) → Patterns MVVM (custom), Dagger 2... → Testing only unit tests

Slide 9

Slide 9 text

What were we doing? → Company iOS first (more resources, earlier releases) → Client Java (and Kotlin later...) → Patterns MVVM (custom), Dagger 2... → Testing only unit tests → Backend no access/influence over APIs

Slide 10

Slide 10 text

How it was supposed to be...

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

How it really was...

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

→ No collaboration between teams

Slide 17

Slide 17 text

→ No collaboration between teams → Completely different release schedules

Slide 18

Slide 18 text

→ No collaboration between teams → Completely different release schedules → No Android internal dogfood

Slide 19

Slide 19 text

→ No collaboration between teams → Completely different release schedules → No Android internal dogfood → 100% oriented APIs towards iOS

Slide 20

Slide 20 text

→ No collaboration between teams → Completely different release schedules → No Android internal dogfood → 100% oriented APIs towards iOS → Zero confidence in success

Slide 21

Slide 21 text

We needed a change

Slide 22

Slide 22 text

A big change

Slide 23

Slide 23 text

A new opportunity was presented to us: A redesign was coming that would allow us to challenge business processes and technology choices

Slide 24

Slide 24 text

Doing the same thing would only lead to failure...

Slide 25

Slide 25 text

We had a very ambitious goal

Slide 26

Slide 26 text

We want to be able to regularly release our products across all brands, all platforms and all regions simultaneously, with the same feature capabilities.

Slide 27

Slide 27 text

What can we do better?

Slide 28

Slide 28 text

What can we do better? → Robust and predictable APIs

Slide 29

Slide 29 text

What can we do better? → Robust and predictable APIs → Never say no to designers

Slide 30

Slide 30 text

What can we do better? → Robust and predictable APIs → Never say no to designers → Be full stack and open to collaboration

Slide 31

Slide 31 text

What can we do better? → Robust and predictable APIs → Never say no to designers → Be full stack and open to collaboration → Better understanding of business goals

Slide 32

Slide 32 text

What can we do better? → Robust and predictable APIs → Never say no to designers → Be full stack and open to collaboration → Better understanding of business goals → Shorter feature cycle times

Slide 33

Slide 33 text

What can we do better? → Robust and predictable APIs → Never say no to designers → Be full stack and open to collaboration → Better understanding of business goals → Shorter feature cycle times → Improve our developer experience

Slide 34

Slide 34 text

Our mantra Create a platform that is developer friendly, scalable and performant, which provides safe experimentation and continuos deployment.

Slide 35

Slide 35 text

After a 6 month long research...

Slide 36

Slide 36 text

...our conclusion was clear

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

What is Flutter? Flutter is Google's UI toolkit for building beautiful, natively compiled applications for mobile, web and desktop from a single codebase.

Slide 39

Slide 39 text

void main() => runApp(MyApp()); class MyApp extends StatelessWidget { @override Widget build(BuildContext context) { return MaterialApp(home: MyHomePage()); } } class MyHomePage extends StatefulWidget { @override _MyHomePageState createState() => _MyHomePageState(); } class _MyHomePageState extends State { int _counter = 0; void _incrementCounter() { setState(() { _counter++; }); } @override Widget build(BuildContext context) { return Scaffold( appBar: AppBar(title: Text('Counter')), body: Center( child: Column( mainAxisAlignment: MainAxisAlignment.center, children: [ Text('You have pushed the button this many times:'), Text('$_counter'), ], ), ), floatingActionButton: FloatingActionButton( onPressed: _incrementCounter, child: Icon(Icons.add), ), ); } }

Slide 40

Slide 40 text

void main() => runApp(MyApp()); class MyApp extends StatelessWidget { @override Widget build(BuildContext context) { return MaterialApp(home: MyHomePage()); } } class MyHomePage extends StatefulWidget { @override _MyHomePageState createState() => _MyHomePageState(); } class _MyHomePageState extends State { int _counter = 0; void _incrementCounter() { setState(() { _counter++; }); } @override Widget build(BuildContext context) { return Scaffold( appBar: AppBar(title: Text('Counter')), body: Center( child: Column( mainAxisAlignment: MainAxisAlignment.center, children: [ Text('You have pushed the button this many times:'), Text('$_counter'), ], ), ), floatingActionButton: FloatingActionButton( onPressed: _incrementCounter, child: Icon(Icons.add), ), ); } }

Slide 41

Slide 41 text

void main() => runApp(MyApp()); class MyApp extends StatelessWidget { @override Widget build(BuildContext context) { return MaterialApp(home: MyHomePage()); } } class MyHomePage extends StatefulWidget { @override _MyHomePageState createState() => _MyHomePageState(); } class _MyHomePageState extends State { int _counter = 0; void _incrementCounter() { setState(() { _counter++; }); } @override Widget build(BuildContext context) { return Scaffold( appBar: AppBar(title: Text('Counter')), body: Center( child: Column( mainAxisAlignment: MainAxisAlignment.center, children: [ Text('You have pushed the button this many times:'), Text('$_counter'), ], ), ), floatingActionButton: FloatingActionButton( onPressed: _incrementCounter, child: Icon(Icons.add), ), ); } }

Slide 42

Slide 42 text

void main() => runApp(MyApp()); class MyApp extends StatelessWidget { @override Widget build(BuildContext context) { return MaterialApp(home: MyHomePage()); } } class MyHomePage extends StatefulWidget { @override _MyHomePageState createState() => _MyHomePageState(); } class _MyHomePageState extends State { int _counter = 0; void _incrementCounter() { setState(() { _counter++; }); } @override Widget build(BuildContext context) { return Scaffold( appBar: AppBar(title: Text('Counter')), body: Center( child: Column( mainAxisAlignment: MainAxisAlignment.center, children: [ Text('You have pushed the button this many times:'), Text('$_counter'), ], ), ), floatingActionButton: FloatingActionButton( onPressed: _incrementCounter, child: Icon(Icons.add), ), ); } }

Slide 43

Slide 43 text

void main() => runApp(MyApp()); class MyApp extends StatelessWidget { @override Widget build(BuildContext context) { return MaterialApp(home: MyHomePage()); } } class MyHomePage extends StatefulWidget { @override _MyHomePageState createState() => _MyHomePageState(); } class _MyHomePageState extends State { int _counter = 0; void _incrementCounter() { setState(() { _counter++; }); } @override Widget build(BuildContext context) { return Scaffold( appBar: AppBar(title: Text('Counter')), body: Center( child: Column( mainAxisAlignment: MainAxisAlignment.center, children: [ Text('You have pushed the button this many times:'), Text('$_counter'), ], ), ), floatingActionButton: FloatingActionButton( onPressed: _incrementCounter, child: Icon(Icons.add), ), ); } }

Slide 44

Slide 44 text

...but why Flutter? Flutter was chosen not only because we thought it was going to meet the needs, but because it was a risk mitigation strategy. We were considerably more likely to be successful and deliver the product we were asked to deliver by using Flutter. — Larry McKenzie, Tech Lead @ eBay Motors

Slide 45

Slide 45 text

What does Flutter have to offer?

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

When we tried Flutter in 2018

Slide 50

Slide 50 text

When we tried Flutter in 2018 → Fast development: Hot Reload

Slide 51

Slide 51 text

When we tried Flutter in 2018 → Fast development: Hot Reload → Expressive UIs: Highly composable widgets

Slide 52

Slide 52 text

When we tried Flutter in 2018 → Fast development: Hot Reload → Expressive UIs: Highly composable widgets → Native performance: 60fps

Slide 53

Slide 53 text

When we tried Flutter in 2018 → Fast development: Hot Reload → Expressive UIs: Highly composable widgets → Native performance: 60fps → Testing: incredible tooling out of the box

Slide 54

Slide 54 text

When we tried Flutter in 2018 → Fast development: Hot Reload → Expressive UIs: Highly composable widgets → Native performance: 60fps → Testing: incredible tooling out of the box → Works on any UI environment

Slide 55

Slide 55 text

Flutter is like Picasso you can ask it to paint anything, anywhere, and it will deliver outstanding results

Slide 56

Slide 56 text

What about Dart?

Slide 57

Slide 57 text

What about Dart? → Client-optmized language for fast apps on any platform

Slide 58

Slide 58 text

What about Dart? → Client-optmized language for fast apps on any platform → Feels natural and familiar

Slide 59

Slide 59 text

What about Dart? → Client-optmized language for fast apps on any platform → Feels natural and familiar → Future API (async-await)

Slide 60

Slide 60 text

What about Dart? → Client-optmized language for fast apps on any platform → Feels natural and familiar → Future API (async-await) → Isolate-based concurrency

Slide 61

Slide 61 text

Future fetchTemperate() async { final response = await http.get('weather.com'); if (response.statusCode == 200) { print('Temperature: ${response.body}'); } else { throw Exception('Failed fetching temperature'); } }

Slide 62

Slide 62 text

What about the Dart & Flutter community?

Slide 63

Slide 63 text

What about the Dart & Flutter community? → Vibrant and welcoming community

Slide 64

Slide 64 text

What about the Dart & Flutter community? → Vibrant and welcoming community → Started Chicago Flutter

Slide 65

Slide 65 text

What about the Dart & Flutter community? → Vibrant and welcoming community → Started Chicago Flutter → Incredible documentation and tutorials

Slide 66

Slide 66 text

What about the Dart & Flutter community? → Vibrant and welcoming community → Started Chicago Flutter → Incredible documentation and tutorials → Amazing conferences

Slide 67

Slide 67 text

... and many other benefits

Slide 68

Slide 68 text

... and many other benefits → UI described as a tree (widget tree)

Slide 69

Slide 69 text

... and many other benefits → UI described as a tree (widget tree) → Multiple state management solutions

Slide 70

Slide 70 text

... and many other benefits → UI described as a tree (widget tree) → Multiple state management solutions → 3 levels of testing without 3rd party dependencies

Slide 71

Slide 71 text

In 2020...

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

Very Good Ventures is...

Slide 74

Slide 74 text

Very Good Ventures is... → 100% focused on Flutter

Slide 75

Slide 75 text

Very Good Ventures is... → 100% focused on Flutter → First in Flutter: Hamilton. The Musical

Slide 76

Slide 76 text

Very Good Ventures is... → 100% focused on Flutter → First in Flutter: Hamilton. The Musical → Experts in Flutter: Google, The New York Times, Betterment, Policygenius, Good Money...

Slide 77

Slide 77 text

How do we use Flutter?

Slide 78

Slide 78 text

How do we use Flutter? → 3-tier architecture (data, domain, UI)

Slide 79

Slide 79 text

How do we use Flutter? → 3-tier architecture (data, domain, UI) → flutter_bloc

Slide 80

Slide 80 text

How do we use Flutter? → 3-tier architecture (data, domain, UI) → flutter_bloc → 100% test coverage

Slide 81

Slide 81 text

How do we use Flutter? → 3-tier architecture (data, domain, UI) → flutter_bloc → 100% test coverage → Strong focus on automation

Slide 82

Slide 82 text

I have worked with Ruby on Rails, Angular, iOS (Objective-C & Swift), Android (Java & Kotlin)... and nothing has brought more happiness to me than Flutter

Slide 83

Slide 83 text

Flutter has made me a better person... and a better developer

Slide 84

Slide 84 text

It has been a pleasure!

Slide 85

Slide 85 text

It has been a pleasure! → Very Good Ventures ([email protected])

Slide 86

Slide 86 text

It has been a pleasure! → Very Good Ventures ([email protected]) → Google Developer Expert (GDE) for Flutter

Slide 87

Slide 87 text

It has been a pleasure! → Very Good Ventures ([email protected]) → Google Developer Expert (GDE) for Flutter → Instructor @ Caster.IO (Testing Fundamentals of Flutter)

Slide 88

Slide 88 text

It has been a pleasure! → Very Good Ventures ([email protected]) → Google Developer Expert (GDE) for Flutter → Instructor @ Caster.IO (Testing Fundamentals of Flutter) → Chicago Flutter Meetup

Slide 89

Slide 89 text

The End Happy Coding! !"