Functional Android
summary
Shows concrete refactors: turning an impure blender/cook example into pure functions so outputs depend only on inputs, replacing shared mutable burger state that caused wrong toppings with val / data class copy and immutable lists, and using RxJava merge/schedulers to run topping tasks concurrently without races. Claims this yields easier testing and fewer surprises; demonstrates the buggy mutable version and the fixed immutable version, and notes performance cost is usually negligible.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:00Who am I
- 1:35Why Kotlin
- 2:08Functional Programming
- 3:45Pure Functions
- 4:52Blend Functions
- 5:57No Side Effects
- 7:40Side Effects
- 8:30Order
- 10:33Spring
- 11:09immutability
- 12:21immutable
- 13:27if statement
- 14:13mutable objects
- 16:00copying objects
- 19:03merge
- 19:40immutable burger
- 21:21shared preferences
- 22:30curly braces
- 23:54abstract object
related talks
34mFunctional Android
29mLet's get functional
42mIngredients for a healthy codebase (en)
42mWorking Effectively with (Android) Legacy Code
32mFunctional Programming on Android
37mRedux on Android, the nitty gritty
31mPatterns for Safe Refactoring of Android Apps
40mComedy Talk – Better Android Development (BAD)