Platform types and null safety in Kotlin - Mini Project: Build & Apply

Platform types and null safety

📖 Scenario: You are working on a Kotlin app that interacts with Java code. Java methods can return values that might be null, but Kotlin needs you to handle nulls safely.This project will help you understand how Kotlin treats platform types from Java and how to use null safety features to avoid crashes.

🎯 Goal: Build a Kotlin program that calls a Java method returning a platform type, then safely handles possible null values using Kotlin's null safety features.

📋 What You'll Learn

Create a Kotlin variable to hold a platform type value returned from a Java method

Create a nullable Kotlin variable to hold the same value safely

Use a safe call operator to access the length of the string safely

Print the length or a message if the value is null

💡 Why This Matters

🌍 Real World

Many Kotlin apps use Java libraries. Understanding platform types helps avoid crashes from unexpected nulls.

💼 Career

Handling null safety and platform types is essential for Kotlin developers working with mixed Java-Kotlin codebases.

1

Create a Kotlin variable with a platform type value

Create a Kotlin variable called platformString and assign it the value returned by the Java method JavaClass.getPlatformString().

Kotlin

class JavaClass {
    companion object {
        @JvmStatic
        fun getPlatformString(): String? = null
    }
}

fun main() {
    // Create platformString variable assigned from JavaClass.getPlatformString()
    // Your code here
}

Hint

Use val platformString = JavaClass.getPlatformString() to get the platform type value.

2

Create a nullable Kotlin variable to hold the platform type safely

Create a nullable Kotlin variable called safeString and assign it the value of platformString.

Kotlin

class JavaClass {
    companion object {
        @JvmStatic
        fun getPlatformString(): String? = null
    }
}

fun main() {
    val platformString = JavaClass.getPlatformString()
    // Create nullable variable safeString assigned from platformString
    // Your code here
}

Hint

Declare safeString as nullable String and assign platformString to it.

3

Use safe call operator to get length safely

Create a variable called length and assign it the length of safeString using the safe call operator ?..

Kotlin

class JavaClass {
    companion object {
        @JvmStatic
        fun getPlatformString(): String? = null
    }
}

fun main() {
    val platformString = JavaClass.getPlatformString()
    val safeString: String? = platformString
    // Create length variable using safe call operator on safeString
    // Your code here
}

Hint

Use safeString?.length to get length safely without errors if null.

4

Print the length or a message if null

Print the value of length if it is not null; otherwise, print "Length is unknown" using the Elvis operator ?:.

Kotlin

class JavaClass {
    companion object {
        @JvmStatic
        fun getPlatformString(): String? = null
    }
}

fun main() {
    val platformString = JavaClass.getPlatformString()
    val safeString: String? = platformString
    val length = safeString?.length
    // Print length or "Length is unknown" if length is null
    // Your code here
}

Hint

Use println(length ?: "Length is unknown") to print length or fallback message.

Practice

1. What is a platform type in Kotlin when interacting with Java code?

easy

A. A type with unknown nullability coming from Java code

B. A Kotlin type that is always non-nullable

C. A Kotlin type that is always nullable

D. A special Kotlin type used only in multiplatform projects

Solution

1. Step 1: Understand Kotlin-Java interoperability

   Kotlin calls Java code but Java does not specify nullability clearly.

2. Step 2: Define platform type meaning

   Platform types represent types from Java with unknown nullability, so Kotlin treats them flexibly but unsafely.

3. Final Answer:

   A type with unknown nullability coming from Java code -> Option A

4. Quick Check:

   Platform type = unknown nullability [OK]

Hint: Platform types come from Java with unclear null info [OK]

Common Mistakes:

• Thinking platform types are always nullable
• Assuming platform types are always non-nullable
• Confusing platform types with Kotlin multiplatform types

2. Which Kotlin syntax correctly declares a variable that can hold a platform type from Java and safely handle nulls?

easy

A. val name: String = javaMethod()

B. val name: String!! = javaMethod()

C. val name: String? = javaMethod()

D. val name: String? = null!!

Solution

1. Step 1: Recognize platform type usage

   Java method returns a platform type, which can be nullable or not.

2. Step 2: Choose safe Kotlin declaration

   Declaring as nullable String? allows safe null handling from platform types.

3. Final Answer:

   val name: String? = javaMethod() -> Option C

4. Quick Check:

   Nullable type for platform type = safe [OK]

Hint: Use nullable type to safely hold platform types [OK]

Common Mistakes:

• Using non-nullable type without null checks
• Using !! which causes exceptions if null
• Using invalid syntax like null!!

3. Given this Kotlin code calling a Java method returning a platform type:

fun printLength() {
    val text: String = javaMethod()
    println(text.length)
}

What happens if javaMethod() returns null?

medium

A. The program compiles but does nothing

B. The program prints 0

C. The program prints "null"

D. The program throws a NullPointerException at runtime

Solution

1. Step 1: Analyze variable declaration

   Variable text is declared as non-nullable String but assigned platform type from Java.

2. Step 2: Consider null return from Java

   If javaMethod() returns null, Kotlin does not check at compile time, but accessing text.length causes NullPointerException.

3. Final Answer:

   The program throws a NullPointerException at runtime -> Option D

4. Quick Check:

   Non-null platform type + null value = runtime exception [OK]

Hint: Non-null platform types can cause runtime null errors [OK]

Common Mistakes:

• Assuming Kotlin prevents null assignment from platform types
• Thinking it prints 0 or "null" instead of crashing
• Ignoring runtime exceptions from platform types

4. Identify the error in this Kotlin code using a platform type:

val length: Int = javaMethod()?.length

where javaMethod() returns a platform type String!.

medium

A. The expression can return null but assigned to non-nullable Int

B. No error, code is correct

C. Platform types cannot be assigned to Int variables

D. Safe call operator ?. cannot be used on platform types

Solution

1. Step 1: Understand the expression type

   javaMethod() returns platform type String!, so javaMethod()?.length returns Int? (nullable Int).

2. Step 2: Check assignment compatibility

   Assigning nullable Int? to non-nullable Int variable length causes a type mismatch error.

3. Final Answer:

   The expression can return null but assigned to non-nullable Int -> Option A

4. Quick Check:

   Nullable result assigned to non-null variable = error [OK]

Hint: Nullable result must not assign to non-null variable [OK]

Common Mistakes:

• Thinking safe call ?. is invalid on platform types
• Ignoring nullability mismatch in assignment
• Assuming platform types cannot be used with Int

5. You have a Java method String getName() that may return null. How should you declare and use it in Kotlin to avoid null pointer exceptions and keep null safety?

hard

A. Declare as val name: String = javaMethod() and use name.length

B. Declare as val name: String? and check if (name != null) before use

C. Declare as val name: String!! and use name.length directly

D. Declare as val name: String and use name?.length ?: 0

Solution

1. Step 1: Recognize Java method nullability

   Java method may return null, so Kotlin platform type is uncertain.

2. Step 2: Choose safe Kotlin declaration and usage

   Declare as nullable String? and check for null before accessing properties to avoid exceptions.

3. Final Answer:

   Declare as val name: String? and check if (name != null) before use -> Option B

4. Quick Check:

   Nullable declaration + null check = safe usage [OK]

Hint: Use nullable type and explicit null check for Java returns [OK]

Common Mistakes:

• Using non-nullable type without null checks
• Using !! which risks runtime exceptions
• Misusing safe call with non-nullable declaration