Why Kotlin annotations for Java callers (@JvmStatic, @JvmField)? - Purpose & Use Cases

The Big Idea

What if your Kotlin code could speak Java's language perfectly without extra hassle?

The Scenario

Imagine you wrote a Kotlin class with some functions and properties, but now you need to use it from Java code. You try to call those Kotlin members from Java, but the syntax is confusing and sometimes you can't access them directly.

The Problem

Without special annotations, Java callers see Kotlin code differently. Static functions in Kotlin become instance methods in Java, and properties become getter/setter methods. This makes Java code verbose and error-prone, and sometimes you can't access what you want easily.

The Solution

Using Kotlin annotations like @JvmStatic and @JvmField tells the compiler to generate Java-friendly code. @JvmStatic makes functions appear as static methods in Java, and @JvmField exposes properties as public fields. This makes calling Kotlin code from Java simple and natural.

Before vs After

✗ Before

class Utils {
    companion object {
        fun greet() = "Hello"
        val version = "1.0"
    }
}
// Java call: Utils.Companion.greet(); Utils.Companion.getVersion();

✓ After

class Utils {
    companion object {
        @JvmStatic fun greet() = "Hello"
        @JvmField val version = "1.0"
    }
}
// Java call: Utils.greet(); Utils.version;

What It Enables

This lets Kotlin code feel natural and easy to use from Java, improving interoperability and reducing confusion.

Real Life Example

When building Android apps, you often mix Kotlin and Java. Using these annotations helps Java parts call Kotlin utilities or constants cleanly without awkward syntax.

Key Takeaways

Calling Kotlin from Java can be confusing without help.

@JvmStatic and @JvmField make Kotlin members look like normal Java static methods and fields.

This improves code clarity and reduces errors when mixing Kotlin and Java.

Practice

1. What is the main purpose of the @JvmStatic annotation in Kotlin when called from Java?

easy

A. To convert Kotlin lambdas into Java anonymous classes

B. To expose Kotlin properties as public fields in Java

C. To make a Kotlin function in a companion object appear as a static method in Java

D. To mark a Kotlin class as a Java interface

Solution

1. Step 1: Understand the role of @JvmStatic

   @JvmStatic makes functions inside Kotlin companion objects look like static methods in Java, so Java code can call them without an instance.

2. Step 2: Differentiate from @JvmField

   @JvmField exposes properties as fields, not functions. The question asks about functions, so @JvmStatic is correct.

3. Final Answer:

   To make a Kotlin function in a companion object appear as a static method in Java -> Option C

4. Quick Check:

   @JvmStatic = static method in Java [OK]

Hint: Remember: @JvmStatic = static method in Java [OK]

Common Mistakes:

• Confusing @JvmStatic with @JvmField
• Thinking @JvmStatic applies to properties
• Assuming it changes Kotlin class types

2. Which of the following is the correct way to expose a Kotlin property as a public field accessible directly from Java?

easy

A. Annotate the property with @JvmStatic

B. Annotate the property with @JvmField

C. Declare the property as val without annotations

D. Use @JvmOverloads annotation

Solution

1. Step 1: Identify the annotation for exposing fields

   @JvmField exposes Kotlin properties as public fields for direct Java access, bypassing getters/setters.

2. Step 2: Eliminate other options

   @JvmStatic applies to functions, not properties. @JvmOverloads is for default parameters. val alone does not expose as field.

3. Final Answer:

   Annotate the property with @JvmField -> Option B

4. Quick Check:

   @JvmField = public field in Java [OK]

Hint: Use @JvmField to expose properties as fields [OK]

Common Mistakes:

• Using @JvmStatic on properties
• Assuming val exposes public field automatically
• Confusing @JvmOverloads with field exposure

3. Given the Kotlin code below, what will be the output when called from Java?

class Example {
    companion object {
        @JvmStatic
        fun greet() = "Hello from static"

        fun greetInstance() = "Hello from instance"
    }
}

// Java code:
System.out.println(Example.greet());
System.out.println(Example.Companion.greetInstance());

medium

A. Compilation error\nHello from instance

B. Hello from static\nCompilation error

C. Compilation error\nCompilation error

D. Hello from static\nHello from instance

Solution

1. Step 1: Understand @JvmStatic effect on Java calls

   @JvmStatic makes greet() callable as a static method on Example class directly from Java.

2. Step 2: Understand companion object function call

   greetInstance() is not annotated, so Java must call it via Example.Companion instance.

3. Final Answer:

   Hello from static\nHello from instance -> Option D

4. Quick Check:

   @JvmStatic allows direct static call, others via Companion [OK]

Hint: @JvmStatic = call directly on class; else use Companion [OK]

Common Mistakes:

• Assuming all companion functions are static in Java
• Trying to call unannotated functions as static
• Ignoring the Companion object in Java calls

4. Identify the error in the Kotlin code below if the goal is to allow Java code to access count as a public field:

class Counter {
    companion object {
        var count = 0
    }
}

medium

A. Missing @JvmField on count

B. Missing @JvmStatic on count

C. Companion object cannot have properties

D. count must be declared as val not var

Solution

1. Step 1: Understand property exposure to Java

   To expose a Kotlin property as a public field in Java, it must be annotated with @JvmField.

2. Step 2: Check annotations and property modifiers

   @JvmStatic applies to functions, not properties. Companion objects can have properties. var is allowed.

3. Final Answer:

   Missing @JvmField on count -> Option A

4. Quick Check:

   Expose property as field = use @JvmField [OK]

Hint: Use @JvmField on properties for Java field access [OK]

Common Mistakes:

• Using @JvmStatic on properties
• Thinking companion objects can't have properties
• Confusing var and val for Java exposure

5. You want to create a Kotlin utility class with a companion object that has a constant integer MAX accessible as a static field from Java, and a function printMax() callable as a static method from Java. Which is the correct Kotlin code?

hard

A. class Utils {
companion object {
@JvmField
val MAX = 100
@JvmStatic
fun printMax() = println(MAX)
}
}

B. class Utils {
companion object {
val MAX = 100
fun printMax() = println(MAX)
}
}

C. class Utils {
companion object {
@JvmStatic
val MAX = 100
@JvmField
fun printMax() = println(MAX)
}
}

D. class Utils {
companion object {
const val MAX = 100
fun printMax() = println(MAX)
}
}

Solution

1. Step 1: Expose constant as static field

   Use @JvmField on val MAX to expose it as a static field in Java.

2. Step 2: Expose function as static method

   Use @JvmStatic on printMax() to make it callable as a static method from Java.

3. Step 3: Verify other options

   class Utils { companion object { val MAX = 100 fun printMax() = println(MAX) } } lacks annotations, so Java calls require Companion. class Utils { companion object { @JvmStatic val MAX = 100 @JvmField fun printMax() = println(MAX) } } swaps annotations incorrectly. class Utils { companion object { const val MAX = 100 fun printMax() = println(MAX) } } uses const val but no @JvmStatic on function.

4. Final Answer:

   The code with @JvmField on MAX and @JvmStatic on printMax() -> Option A

5. Quick Check:

   @JvmField for fields, @JvmStatic for static methods [OK]

Hint: Use @JvmField for fields and @JvmStatic for methods [OK]

Common Mistakes:

• Swapping @JvmField and @JvmStatic annotations
• Omitting annotations and expecting static access
• Using const val without @JvmStatic on functions