Quick Compose Navigation question: we’re seeing du...

# compose

[Soumen pal]

Quick Compose Navigation question: we’re seeing duplicate back navigation when users tap the back icon (or system back) multiple times quickly on a screen. We currently guard with a local isBackClickEnabled flag and disable back
after first click until navigation completes.
How are others handling this in production KMP/Compose apps?

1. UI-level debounce/disable click
2. NavController-level singleTop/route guard
3. ViewModel event gate
4. Other pattern

Also, what edge cases have you hit (failed pop, recomposition reset, process death, animation delay, etc.) and what ended up being the most reliable fix?”

[Ian Lake]

There's already an API to solve exactly this problem: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1720237053836149?thread_ts=1720177604.098429&cid=CJLTWPH7S

[GeorgeS-Litesoft]

Ian,

I'm not new to Kotlin, but I am new to compose, and plan to generate a number of CMP application.

It seems strange to use an 'androidx' library to solve a problem that I would expected to be a Compose problem in a multi-platform project.

The Version 2.11.0-alpha(s) in 2026 indicate that there is or soon will be support for KMP, but we must still pull in an 'androidx' library...

Version 2.10 seems to be the latest non-Alpha.

So my question: can an Android library be referenced/used by non-Android targets?

[Ian Lake]

There's a section in those Lifecycle 2.8.0 notes called "Lifecycle Kotlin Multiplatform Compatibility". Lifecycle has supported KMP for years

[ursus]

@Soumen pal stupid question but how do you know navigation actually completed