rxjava-migration

Migrate incrementally from leaf nodes upward: convert data sources first using kotlinx-coroutines-rx3 bridges like await() and asFlow(), then repositories, use cases, and ViewModels. Map Single to suspend functions, Observable to Flow, and Subjects to SharedFlow or StateFlow.

Single maps to a suspend function returning T, Maybe maps to a suspend function returning a nullable T, 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 you always have an initial value and need .value access. Use MutableSharedFlow with replay = 1 when the stream may start empty and you do not need synchronous value access. The choice depends on your semantics, so confirm before migrating.

Use Flow's retryWhen { cause, attempt -> } operator, where cause is the Throwable and attempt is the zero-based attempt index. Do not use retry(n) with a predicate expecting an index, since that lambda receives the Throwable, not a count.

flatMapLatest cancels the previous inner stream when a new upstream value arrives, which can abort in-flight write operations mid-transaction. It is safe for reads like search queries, but confirm cancellation safety with the developer before using it for writes.

Yes, using the kotlinx-coroutines-rx3 library with bridges like asFlow(), await(), and asObservable(). Keep interop strictly at layer boundaries, never mix both models within the same function body, and remove bridges after each layer is fully migrated.