More VIPER, Baby

Talking about iOS VIPER and Clean Architecture history, real usage, options, and best practices.
#oleksiiholub #svitlasmarttalk #iosdevelopment #iosmeetup
Oleksii Holub (Ukraine, Kyiv) works as a Mobile Architect and Team Lead. In this speech, he talks about how to use VIPER architecture in iOS application development.
"Svitla Smart Talk, iOS" meetup was held on 23.06.2020 in Zoom.
Announce: https://dou.ua/calendar/32844/
Main part: https://www.youtube.com/watch?v=zwL-lUrgVm4
Q&A part: https://www.youtube.com/watch?v=Vi4zaPiKo0Q

Transcript

1. Oleksii Holub 
 Mobile architect, Team Lead, iOS Developer in 
 NDA
2. DONUT MEDIA JAMES
4. OLEKSII HOLUB, 2020 MORE VIPER, BABY!
5. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
6. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
7. JUNIOR IOS DEVELOPER WRITES COMMENT ON THE FORUM “GOOD OL’ MVC IS THE BEST”
8. SENIOR IOS DEVELOPER IS READING JUNIOR’S COMMENT “GOOD OL’ MVC IS THE BEST”
9. TWO YEARS LATER ON THE SAME FORUM “VIPER IS THE BEST”
10. SENIOR IOS DEVELOPER IS READING JUNIOR’S COMMENT “VIPER IS THE BEST”
11. WHICH PROBLEM VIPER SOLVES
12. WHICH PROBLEM VIPER SOLVES APPLE’S MVC IS SPECIAL
13. APPLE’S MVC WHAT YOU’D EXPECT
14. APPLE’S MVC WHAT YOU GOT IN REALITY
15. INCAPSULATION YourViewController interface internals
16. INCAPSULATION interface internals ENDS WITH GOD OBJECT YourViewController
17. PROBLEM! YourClass interface
18. INCAPSULATION interface internals ENDS WITH GOD OBJECT worker worker YourViewController
19. YOUR NEW ARCHITECTURE interface internals COMPLIANT WITH SOLID worker class worker class YourViewController
20. TESTS ARE EVERYWHERE! interface internals worker class worker class YourViewController covered with unit tests covered with unit tests private de fi nitions covered with unit tests
21. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
22. UNCLE BOB’S “CLEAN ARCHITECTURE”
23. WHICH PROBLEM VIPER SOLVES UNCLE BOB’S “CLEAN ARCHITECTURE”
24. BIT OF HISTORY YourClass interface
25. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
26. MVP IS BADDD
27. MVP IS BADDD
28. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
29. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
30. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET JOHN REID
 
 Test Driven Development for iOS
31. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
32. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
33. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
34. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
35. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
36. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
37. WHY VIPER - SEPARATION OF CONCERNS - HIGHEST POSSIBLE TESTABILITY - HIGHEST POSSIBLE ABSTRACTION - SOLID COMPLIANT - EASY TO MIX WITH EVERYTHING ELSE - BEST CHOICE FOR TDD - IMPROVES OOP THROUGH TESTS - BEST FOR REFACTORING - BEST OF ALL ON THE MARKET
38. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
39. AVAILABLE VIPER OPTIONS
40. AVAILABLE VIPER OPTIONS +WIREFRAME
41. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
42. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
43. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
44. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
45. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
46. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
47. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
48. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
49. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
50. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
51. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
52. • THAT’S NEITHER A KISS NOR DRY! • TIGHT INTEGRATION IN THE PROJECT • THE STORYBOARD BECOMES AN ISSUE • VIEWCONTROLLER IS STILL THERE • BOILERPLATE CODE • A LOT OF ABSOLUTELY IDENTICAL ROUTERS (AND PRESENTERS) • IN THE FAST CHANGING STARTUP ENVIRONMENT YOU’LL HAVE TO REWRITE A LOT OF STUFF • DEFINITELY NOT THE BEST CHOICE FOR NEITHER POC NOR MVP • IF YOU DON’T CARE ABOUT UNIT TESTS - FORGET IT • YOUR JUNIOR DEVELOPERS WILL STRUGGLE CONS
53. CONS
54. CONS PRESENTER IS BUSY
55. CONS TWO WAY COMMUNICATION
56. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
57. COOKING IT IN AN EFFICIENT WAY
58. COOKING IT IN AN EFFICIENT WAY ONE WAY!
59. COOKING IT IN AN EFFICIENT WAY VIP OR CLEAN ARCHITECTURE
60. COOKING IT IN AN EFFICIENT WAY ONE WAY!
61. COOKING IT IN AN EFFICIENT WAY ONE WAY!
62. COOKING IT IN AN EFFICIENT WAY
63. COOKING IT IN AN EFFICIENT WAY fetchContacts()
64. COOKING IT IN AN EFFICIENT WAY fetchContacts() fetchOrUpdateContacts()
65. COOKING IT IN AN EFFICIENT WAY fetchContacts() fetchOrUpdateContacts() updateContacts()
66. COOKING IT IN AN EFFICIENT WAY fetchContacts() fetchOrUpdateContacts() updateContacts() refreshTableView()
67. COOKING IT IN AN EFFICIENT WAY ONE WAY DATA FLOW
68. COOKING IT IN AN EFFICIENT WAY VIEW LOGIC AND BUSINESS LOGIC SEPARATION
69. COOKING IT IN AN EFFICIENT WAY BETTER DOMAIN SEPARATION
70. COOKING IT IN AN EFFICIENT WAY ASYNC LOGIC SEPARATION
71. COOKING IT IN AN EFFICIENT WAY GOOD INCAPSULATION AND SMALL METHODS
72. COOKING IT IN AN EFFICIENT WAY VIEWCONTRTOLLER
73. COOKING IT IN AN EFFICIENT WAY VIEWCONTRTOLLER
74. COOKING IT IN AN EFFICIENT WAY INTERACTOR
75. COOKING IT IN AN EFFICIENT WAY INTERACTOR
76. COOKING IT IN AN EFFICIENT WAY PRESENTER
77. COOKING IT IN AN EFFICIENT WAY BACK TO VIEWCONTROLLER
78. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
79. IT’S STILL FAR FROM IDEAL ROUTERS ARE CODE DUPLICATION
80. IT’S STILL FAR FROM IDEAL PRESENTER IS ALSO ROUTING
81. IT’S STILL FAR FROM IDEAL ROUTERS ARE CODE DUPLICATION
82. IT’S STILL FAR FROM IDEAL ROUTERS ARE CODE DUPLICATION
83. IT’S STILL FAR FROM IDEAL DUMB PRESENTER
84. IT’S STILL FAR FROM IDEAL DUMB PRESENTER
85. IT’S STILL FAR FROM IDEAL DUMB PRESENTER
86. IT’S STILL FAR FROM IDEAL NO WAY TO GET RID OF VIEWCONTROLLER
87. IT’S STILL FAR FROM IDEAL NO WAY TO GET RID OF VIEWCONTROLLER SPECIFICALLY ON IOS PLATFORM
88. IT’S STILL FAR FROM IDEAL MAYBE SWIFTUI IS THE ANSWER
89. AGENDA 1. WHICH PROBLEM VIPER SOLVES 2. CLEAN ARCHITECTURE.THE BEGINNING 3. WHY VIPER, WHAT THE HELL IS MVP 4. AVAILABLE OPTIONS 5. CONS 6. COOKING IT IN AN EFFICIENT WAY! 7. IT’S STILL FAR FROM IDEAL 8. HOW TO NOT SCREW IT 9. Q&A
90. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
91. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
92. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
93. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
94. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
95. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
96. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
97. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
98. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
99. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
100. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
101. • OOP AND SOLID IS THE BOSS • PRESENTER PRESENTS, DEFINE WHAT “PRESENTS” MEANS • WRITE UNIT TESTS • SEPARATE BUSINESS AND UI LOGIC • DON’T TRY TO USE COORDINATOR INSTEAD OF ROUTERS • DO UI LOGIC IN VIEWCONTROLLER • TRY TO FIND WORST VIPER IMPLEMENTATION • ALWAYS USE COMMON SENSE • SPEND SOME TIME WITH UNCLE BOB’S BOOK • USE UNIFIED METHOD TO IMPLEMENT WIREFRAME • GIVE A TIME TO YOUR JUNIORS HOW TO NOT SCREW IT
102. AAAND YOUR FEEDBACK, PLEASE!
103. Q&A Thank you very much. That’s it. May the force be with you! AND LINKEDIN