Gain insights into RxJava's principles, explore its integration into Android, and discover why it’s the leading reactive library for enhanced app development.

Reactive Programming on Android with RxJava_468 x 60 copy 2.png

tarball.tar.gz

RxJava

Since its inception in 2012, RxJava has slowly gained in popularity for enabling reactive programming on Android. It is now deemed as the go-to and leading reactive library. Many companies have adopted the reactive way of programming, including Google, with its release of Android Architecture Components, which has many reactive elements in its design.

In this course, you will learn the fundamental principles of RxJava which will serve as a foundation for experienced Android developers who are new to the library and want to start integrating it into their apps.

Reactive Programming with RxJava

So far, the `Observable` class has been our focus for enabling reactive programming with RxJava. However, RxJava also offers the following alternative base reactive types.

# Single
In our previous example in [Leaving the Reactive World](https://www.educative.io/courses/reactive-programming-rxjava/rxjavas-consequences-method-signature), we looked at another base reactive type called a `Single`. As mentioned earlier, a `Single` is a special type of `Observable` that only emits a _single_ item rather than a _stream_ of items. 



Consequently, an observer to a `Single`, a `SingleObserver`, has a different signature and only receives the following events:

* The `.onSubscribe()` function is invoked on subscription and a `Disposable` object is passed along, which can be used to unsubscribe from the `Single`.

* The `.onSuccess()` function is invoked when the `Single` has emitted an item.

* The `.onError()` function is invoked when the `Single` has encountered an error.

Learn about the alternative base reactive types of RxJava.

Getting Started

Part 1: RxJava Basics

Reactive Programming

RxJava Core Components

Operators

Multithreading

Part 2: RxJava Advanced

Reactive Modeling on Android

Backpressure

Error Handling

Conclusion

Reactive Everything: Completable, Single, and Maybe

Single