I stumbled upon <https://blog.p-y.wtf/whilesubscribed5000> after watching this video where I was als...

# android

[Colton Idle]

I stumbled upon https://blog.p-y.wtf/whilesubscribed5000 after watching this video where I was also a bit confused by the 5000 magic number.

I was also actually got off-guard that apparently you can use Lazily instead of whileSubcribed(5000) if you use androidx.navigation. What do you all use?

1️⃣ whileSubscribed(5000)
2️⃣ PY's solution of a custom SharingStarted.WhileSubscribedOrRetained
3️⃣ Use navigation with Lazily

[Ian Lake]

1 is the only right choice. Lazily is absolutely, positively the wrong choice (and will keep work going while that screen is on the back stack)

[Colton Idle]

So not even the custom solution? So much learned today! 😄

[Colton Idle]

also makes sense why i couldn't find the Lazily solution in the navigation docs

[Ian Lake]

It is too clever by about 5x and definitely not tested across every API level and OEM customization 🙃

[Anselmo Alexandre]

I would say Lazily is applicable if you using a shared-view-model use-case where you have a flow and you have to keep the stream alive for each fragment/composable that is collecting from that flow, even when that is on back stack. Correct me if I am wrong @Ian Lake

[Hristijan]

I like to think of 5000 not as a magic number but as a time out and that’s what it is

[Rok Oblak]

As I understand, 5000 is a magic number to account for the time most configuration changes need on most devices, i.e. a sluggish old device being rotated, or a very fast navigation to a child route and then back.

[Colton Idle]

I thought 5_000 because that's the ANR threshold