sealed classes for ui state are an anti-pattern - here's why!
Published 5 months ago • 22K plays • Length 9:53Download video MP4
Download video MP3
Similar videos
-
0:58
enum vs. sealed class... this is the difference
-
10:15
sealed classes vs. enum classes vs. sealed interfaces - when to use which?
-
24:38
are one-time events an anti-pattern? - why almost every android dev does it wrong!
-
0:18
sealed classes? nope!
-
18:09
how to make your code clean with kotlin sealed classes
-
0:33
sealed classes vs. enums - this is what you should use
-
0:31
why do we use interfaces?
-
8:04
swift for android, kotlin for ios
-
11:17
kotlin sealed class (with demo source code)
-
15:17
kotlin sealed classes | kotlin tutorial 2019
-
17:06
5 common android anti-patterns that make your code a mess
-
0:59
did you know you could do this with interfaces in kotlin?!
-
0:40
this trick makes your life easier as an android developer
-
1:00
this is what the ::-operator in kotlin is about
-
4:08
sealed classes - kotlin vocabulary
-
12:40
when to use sealed class, how it's different than enum class || android interview question & answer
-
19:04
kotlin sealed classes & custom state managment (vlog)
-
20:53
state holders and state production in the ui layer
-
0:23
this is when you shouldn't use booleans
-
0:44
avoid this fatal coroutine mistake in kotlin
-
0:26
don't use use cases if...
-
27:36
pushing the limits of the server side ui platform with kmp | paulina sadowska