I spent forty minutes debugging a screen that refused to open. The app compiled fine. No red errors anywhere. I'd tap the button, nothing would happen — no crash, no error, just silence. I checked the click listener. I checked the composable. I checked the NavHost. Everything looked right. Then I found it. // Where I registered the screen composable ( "pokemonDetails" ) { .. . } // Where I was navigating to navController . navigate ( "pokemondetails" ) Enter fullscreen mode Exit fullscreen mode One lowercase letter. Details vs details . Forty minutes. And the worst part? The compiler had no idea. It saw two strings and had nothing to say about it. From Kotlin's perspective, both lines were perfectly valid code. That was the day I stopped trusting navigation strings — and started learning about sealed classes.…