Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

DEV

DEV artwork

Kotlin Flow vs. RxJava: Choosing the Right Reactive Stream

Sep 18, 20265 minAudio

Reactive programming on Android means choosing how your app handles asynchronous data - and for most teams, that choice eventually comes down to Kotlin Flow or RxJava. This episode of DEV.co digs into the practical differences between the two libraries, drawing on the Kotlin Flow vs. RxJava comparison article to give developers a clear framework for making that call. Whether you're greenfielding a new app or inheriting a legacy codebase, the tradeoffs are more nuanced than "new vs. old." The episode covers the core concepts engineers need to evaluate before committing to either approach: Cold vs. hot streams: Flow is cold by default - each collector gets a fresh sequence - while RxJava manages hot and cold through subjects and operators, offering flexibility that rewards careful boundary-setting. Backpressure strategies: Flow uses suspending functions to let a slow collector naturally pace the producer; RxJava provides explicit strategies through Flowable and Observable, with different risk profiles depending on which you reach for. Kotlin Flow's strengths: Built for coroutines, Flow brings structured concurrency, predictable lifecycle handling, and readable pipelines - a natural fit for teams already working with suspend functions and coroutine scopes. Where Flow falls short: Its operator catalog is focused, not exhaustive. Edge-case pipeline combinations may require custom extensions, and interop with Java-only modules can be awkward. RxJava's case for staying: A battle-tested operator library, expressive type distinctions (Single, Flowable, Completable, Maybe), and fine-grained scheduler control make RxJava hard to beat in performance-sensitive or heavily Rx-integrated modules. Decision framework and practical tips: The episode lays out when to migrate, when to stay put, and how to manage a hybrid approach safely - including guidance on module boundaries, error-handling audits, and documenting threading contracts. The episode closes with actionable advice that applies regardless of which library you choose: enforce one stream model per module, keep operator chains small and named, and never let exceptions silently disappear into logs. The goal is a codebase that a future teammate can read without a decoder ring. More from the show: if you're thinking about architecture and build hygiene on mobile, check out the episode on Swift Package Manager Best Practices for Modular iOS Architecture and Faster Builds for a complementary take on keeping large codebases maintainable. DEV.co RFP.co

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. The U.S. Has More Data Centers Than the Next 14 Countries Combined

    Nov 20, 20265 minAudio

    The global data center map looks lopsided by any measure - but the full picture is more striking than a simple site count suggests. This episode of DEV.co digs into a newly published graphic analysis showing just how...

    Credit the people on this episode

  2. From $30 Million to $5 Billion: The AI App Explosion by the Numbers

    Nov 18, 20265 minAudio

    The generative AI app market has posted one of the most dramatic growth curves in consumer software history - and the numbers behind that curve reveal a story far more nuanced than the headline figure suggests. This...

    Credit the people on this episode

  3. AI Adoption: Why the Numbers Are So Far Apart

    Nov 15, 20265 minAudio

    A single statistic can make AI feel like a done deal - nearly every organization already on board, the window to act almost closed. But a competing figure from the U.S. Census Bureau tells a starkly different story....

    Credit the people on this episode

  4. 83% of Developers Use AI Tools — But Only 6.6% Actually Trust Them

    Nov 13, 20265 minAudio

    Widespread AI adoption among software developers is no longer a trend to watch - it's the current reality. But a sweeping Stack Overflow survey of nearly 31,000 developers reveals a striking contradiction at the heart...

    Credit the people on this episode

  5. Private RAG Over Microsoft 365: Permissions, Delta Queries, and What Actually Ships

    Nov 11, 20265 minAudio

    Enterprise teams keep hitting the same wall when grounding LLMs on SharePoint and OneDrive: a working prototype that fails the moment security asks who actually owns access to the returned content. This episode of...

    Credit the people on this episode