Why Platform types and null safety in Kotlin? - Purpose & Use Cases

The Big Idea

What if a tiny unknown null could crash your whole app? Learn how Kotlin protects you!

The Scenario

Imagine you are working on a Kotlin app that uses a Java library. You get values from Java code, but you don't know if they can be null or not. You try to use these values directly in Kotlin.

The Problem

Without clear information, you might get unexpected crashes because Kotlin expects non-null values but Java can send nulls. Manually checking every value is slow and easy to forget, causing bugs.

The Solution

Kotlin's platform types let you handle Java values flexibly. Combined with Kotlin's null safety, you can write safer code that clearly shows when a value might be null, avoiding crashes and confusion.

Before vs After

✗ Before

val name: String = javaLib.getName() // might crash if null
println(name.length)

✓ After

val name: String? = javaLib.getName() // Kotlin knows it might be null
println(name?.length ?: 0)

What It Enables

This lets you safely mix Kotlin and Java code, preventing crashes and making your app more reliable.

Real Life Example

When building Android apps, you often use Java libraries. Platform types and null safety help you avoid app crashes caused by unexpected null values from those libraries.

Key Takeaways

Platform types represent uncertain nullability from Java code.

Null safety in Kotlin helps prevent crashes by forcing checks.

Together, they make Kotlin-Java interop safer and easier.