Android RxJava To Coroutines Migration

When To Use

• Use this skill when the request is about: rxjava to coroutines android, observable to flow android, replace composite disposable android.
• Primary outcome: Migrate Android RxJava code to Kotlin coroutines and Flow with safe lifecycle-aware replacements.
• Reach for this skill when the codebase still exposes Single, Observable, schedulers, or disposables and the goal is to move to suspend, Flow, StateFlow, or SharedFlow.
• Read references/patterns.md for the type-mapping matrix and operator red-flag checklist.
• Read references/scenarios.md for staged migration and inventory-first workflows.
• Handoff skills when the scope expands:
• android-modernization-upgrade
• android-coroutines-flow

Workflow

1. Scan the codebase for RxJava imports, base types, subjects, and scheduler usage before changing any API surface.
2. Classify each usage as one-shot work, stream work, hot state, hot events, callback bridging, or backpressure-sensitive work.
3. Replace repository and domain APIs first, then move UI-layer subscriptions to lifecycle-aware collection.
4. Rewrite scheduler and disposable management as dispatcher, scope, structured-concurrency ownership, and lifecycle-aware collection such as repeatOnLifecycle.
5. Leave a checklist for ambiguous operators or custom bridges instead of pretending every chain can be auto-converted safely.

Guardrails