Why do many developers from companies like Netflix, Microsoft, GitHub, New York Times, Square, SoundCloud, SeatGeek turn to RxJava for their mobile apps? Because Rx relieves all the pain associated with reactive applications, and thus allows their developers to focus on providing business value instead of fighting accidental complexity.

Your mobile device is the ultimate event processing machine. It is filled to the brim with sensors like compass, gyroscope, touch and actuators like vibrate and push notifications. Orchestrating these different event sources, typically running on different threads, to create a compelling user application however leads to a painful developer experience.

Understanding helpful abstractions like Activities, Services, processes and threads can be mind boggling. But an even bigger problem is the fact that the Android UI is not thread-safe. This means you must never block the UI thread, yet must access the UI only from the UI thread. Which leads to a paradox where to keep your app responsive you run work one thread,whereas updating the UI with the result of that work must run on another thread. Android provides options such as AsyncTask to help ease this pain, but the model is not composable and often results in code that is unmaintainable and hard to test.

In this practical and hands-on course you will learn from one that took part in inventing Rx how to leverage the RxMobile toolkit to build reactive Android applications that are elegant, testable, and most importantly fun to code. After this course, you will know how to gradually refactor your existing Android apps to leverage Rx, or how to create a clean reactive architecture from scratch.