You need to tell Retrofit that you want to use RxJava 2, using: addCallAdapterFactory(RxJava2CallAdapterFactory.create()) So, for creating your Retrofit object, you will have something like: Retrofit retrofit = new Retrofit.Builder() .baseUrl(SERVICE_ENDPOINT) .addCallAdapterFactory(RxJava2CallAdapterFactory.create()) .build();
Instead of declaring the API call like you did: Observable<MyResponseObject> apiCall(@Body body); You can also declare it like this: Observable<Response<MyResponseObject>> apiCall(@Body body); You will then have a Subscriber like the following: new Subscriber<Response<StartupResponse>>() { @Override public void onCompleted() {} @Override public void onError(Throwable e) { Timber.e(e, “onError: %”, e.toString()); // network errors, e. g. UnknownHostException, … Read more
Regarding the original question, both RxJava and LiveData complement each other really well. LiveData shines on ViewModel layer, with its tight integration with Android lifecycles and ViewModel. RxJava provides more capabilities in transformations (as mentioned by @Bob Dalgleish). Currently, we’re using RxJava in data source and repository layers, and it’s transformed into LiveData (using LiveDataReactiveStreams) … Read more
Great questions, I think the documentation could do with some more detail. io() is backed by an unbounded thread-pool and is the sort of thing you’d use for non-computationally intensive tasks, that is stuff that doesn’t put much load on the CPU. So yep interaction with the file system, interaction with databases or services on … Read more