---
title: "Discussion on \"The 64-Slot Waiting Room: Why flatMapLatest Still Hands Your UI Yesterday's Data\" | Hashnode"
description: "Discussion on \"The 64-Slot Waiting Room: Why flatMapLatest Still Hands Your UI Yesterday's Data\". A slow map after flatMapLatest can replay up to 64 stale values. Here’s how conflate, mapLatest, and identity checks fix it in Kotlin Flow."
url: "https://hashnode.com/posts/the-64-slot-waiting-room-why-flatmaplatest-still-hands-your-ui-yesterday-s-data/6af4a70ce4032a425a9a98a2"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The 64-Slot Waiting Room: Why flatMapLatest Still Hands Your UI Yesterday's Data](https://android-expert.hashnode.dev/the-64-slot-waiting-room-why-flatmaplatest-still-hands-your-ui-yesterday-s-data?utm_source=hashnode&utm_medium=feed)

A slow map after flatMapLatest can replay up to 64 stale values. Here’s how conflate, mapLatest, and identity checks fix it in Kotlin Flow.

Nov 11 · 10 min read · android-expert.hashnode.dev  
Read the article

-   [#android](https://hashnode.com/tag/android)
-   [#kotlin](https://hashnode.com/tag/kotlin)
-   [#coroutines](https://hashnode.com/tag/coroutines)
-   [#architecture](https://hashnode.com/tag/architecture)

## Written by

[Android Expert](https://hashnode.com/@android-expert)

@android-expert · Chennai, India

  
[View profile](https://hashnode.com/@android-expert)

Android Expert· Kotlin, Jetpack Compose & production pitfalls

Android Engineer &amp; Kotlin Advocate. 🚀 Deep dives into Jetpack Compose, Coroutines, and Clean Architecture. Turning complex code into scalable solutions. 🛠️✨

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
