rxjava-migration

Migrate incrementally: convert leaf nodes like API clients first using kotlinx-coroutines-rx3 bridges (await, asFlow), then move upward through repository, use case, and ViewModel layers. Map Single to suspend functions, Observable to Flow, and commit after each layer.

Single maps to a suspend function returning T, Maybe maps to a suspend function returning T? (null when empty), and Completable maps to a suspend function returning Unit. Observable and Flowable both map to Flow, with Flowable requiring explicit backpressure handling.

Use MutableStateFlow when the stream always has an initial value and you need .value access. Use MutableSharedFlow(replay = 1) when the stream may start empty and no .value property is needed. The decision depends on your semantics, so confirm before converting.

Flow's retry(n) predicate receives the Throwable cause, not an attempt index, so treating it as a counter fails to compile. For stateful policies like exponential backoff, use retryWhen { cause, attempt -> } where attempt is the 0-based retry index.

Yes, but only at layer boundaries using the kotlinx-coroutines-rx3 (or rx2) interop library. Do not mix both paradigms within the same function body, and remove the interop bridges once each layer is fully migrated.

subscribeOn maps to flowOn(dispatcher), which affects only upstream operators. observeOn(AndroidSchedulers.mainThread()) has no direct equivalent; collection on the main dispatcher becomes the caller's responsibility, typically via viewModelScope in the ViewModel.