Null Safety Java Interop in Kotlin

Introduction

Null Safety Java Interop is a fundamental concept every Kotlin developer should understand. Kotlin and Java compile to the same JVM bytecode, so you can mix both languages in one project with minimal friction.

Java types are platform types in Kotlin with unknown nullability. In this tutorial you will learn the syntax, walk through a complete example program, study the sample output, and review best practices so you can apply the concept confidently in your own projects.

Definition

• Java types are platform types in Kotlin with unknown nullability.
• Treat platform types carefully or annotate Java with @Nullable/@NotNull.
• Use safe calls when Java may return null.

Syntax

val value = javaMethod() // platform type

Null Safety Java Interop in Kotlin Example Program in Kotlin

fun parseLength(input: String?): Int {
    return input?.length ?: 0
}

fun main(args: Array<String>) {
    println(parseLength("Kotlin"))
    println(parseLength(null))
}

Sample Output

6
0

When to use

Use interop when migrating a Java codebase incrementally or calling mature Java libraries from Kotlin.

How it works

1. The program starts with a main function — the entry point that runs when you execute the file.

2. return input?.length ?: 0 demonstrates null-safe or type-safe Kotlin syntax in action.

3. The println(parseLength("Kotlin")) statement writes a line to the console — this produces part of the sample output below.

4. The println(parseLength(null)) statement writes a line to the console — this produces part of the sample output below.

5. Java types are platform types in Kotlin with unknown nullability.

6. Run the program in IntelliJ IDEA, Android Studio, or with the Kotlin command-line compiler (kotlinc / kotlin). Compare your console output with the sample output shown below.

Best Practices

• Add @JvmStatic, @JvmOverloads, or @JvmField when Java callers need a cleaner API.
• Use @file:JvmName to avoid awkward Kotlin-generated class names in Java.
• Be explicit about nullability with @Nullable / @NonNull annotations for Java consumers.

Common Mistakes

• Skipping the example and only reading the definition — hands-on practice cements the concept.
• Copying syntax without understanding nullable vs non-nullable types or scope rules.
• Ignoring compiler warnings that often point to safer alternatives.

Key Points

• Java types are platform types in Kotlin with unknown nullability.
• Treat platform types carefully or annotate Java with @Nullable/@NotNull.
• Use safe calls when Java may return null.
• Test the example locally and verify the output matches the sample.
• Experiment by changing input values to see how behaviour changes.

Notes

• Nullability annotations help Kotlin and Java agree on which values can be null at boundaries.
• Semicolons at the end of statements are optional in Kotlin.