Kotlin 2.5.0-Beta2 Adds Experimental onTrue, onFalse, and ifOrNull to Simplify If-Else

These helpers are a small but telling step in Kotlin's shift toward expression-oriented, chainable syntax. If they graduate from Beta, Android developers can shed the noise around simple condition checks without adding a dependency.

Kotlin 2.5.0-Beta2 ships three experimental standard library functions designed to cut down on hand-written if-else branching. onTrue() and onFalse() attach to a Boolean receiver, run a lambda only when the value matches, and hand back the original Boolean, which makes them fit for logging, analytics events, or other side effects without changing the flow. ifOrNull() takes a condition and a lambda, executes the lambda only when the condition is true, and returns its result; otherwise it returns null. That covers the common 'return a value if condition holds, else null' pattern that shows up in UI mapping and DTO construction.

The functions are still experimental in this Beta, so using them requires an explicit opt-in via @OptIn(ExperimentalStdlibApi::class) or the compiler flag -opt-in=kotlin.ExperimentalStdlibApi. The Kotlin team has already outlined them in the Beta1 release notes, but production teams should check the latest docs before relying on them, since experimental APIs can change or be dropped. The author's examples lean heavily on Android scenarios: authentication logging, profile phone-number fallback, and API response mapping all become a single chained call instead of a two-branch if-else.