Functional Android
summary
Argues that adopting Kotlin, RxJava, Arrow and MVI yields concrete gains: pure functions with inputs-only behavior let unit tests run without heavy setup, immutable data models eliminate thread races, and higher‑order functions reduce boilerplate. Shows a Buffer viewmodel that maps actions to UI states (errors treated as data), demonstrates a buggy RxJava merge where two threads mutate the same burger then fixes it by returning new immutable burgers, and points to Biscotti espresso helpers that wrap setup/verify steps.
AI-written summary · about
chapters (9)
- 0:00Introduction to functional Android
- 1:12What is functional programming
- 6:13Pure functions and side effects
- 11:30Ordering and concurrency
- 17:13Immutability in practice
- 24:16Concurrency with immutability
- 27:26Higher order functions
- 32:09Tools and resources
- 33:55Q&A and closing
related talks
24mFunctional Android
46mMvRx: Android Development on Autopilot
43mFunctional approach to Android architecture using Kotlin
57mFunctional Android apps
29mModern Android Development using MVI architecture
42mHands on MvRx: Building Real Apps
29mLet's get functional
34mFunctional Programming in Kotlin for AndroidDevs
