Why Reactive Programming?
summary
The talk explains why reactive programming matters for Android apps, discussing reactive paradigms and their benefits for handling asynchronous events and data streams. It mentions technologies commonly used in Android reactive development (such as RxJava/RxAndroid) and compares reactive approaches to traditional callback-based designs to show how they simplify concurrency and event handling.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:17Reactive programming fundamentals
- 7:53Definition and concepts
- 10:22Data flow and propagation
- 12:54Android practical examples
- 16:40State control without variables
- 18:07Callback hell and reactive solution
- 19:14Concurrency with RxJava
- 20:18Benefits and challenges
- 21:00Common problems and solutions
- 22:25Conclusion
related talks
41mThe definite guide to reactive programming in Java
24mBringing Reactive Programming to Java and Microservices
43mFunctional Reactive Programming with Kotlin on Android
48mGoing Reactive, An Android Architectural Journey
43mReactive Programming in Java
45mReactive for the Impatient - A Gentle Intro to Reactive Programming and Systems
01h 42mReactive Programming: creating highly responsive applications
01h 06mReactive or Not Reactive, That Is the Question