Skip to main content

Step-by-Step Explanation: Adding Kotlin to a Java Project

Step-by-Step Explanation: Adding Kotlin to a Java Project

This document explains the steps taken to integrate Kotlin into the existing Java application and call Kotlin code from Java.

1. Project Configuration

Update Version Catalog (libs.versions.toml)

First, we added the Kotlin version and defined the Kotlin JVM plugin and standard library in the Gradle version catalog.

  • File: libs.versions.toml
  • Changes:
    • Added kotlin = "2.4.20" to the [versions] section.
    • Added kotlin-stdlib to the [libraries] section.
    • Added kotlin-jvm to the [plugins] section.

Apply Kotlin Plugin (build.gradle.kts)

Next, we applied the Kotlin JVM plugin to the application module and added the standard library dependency.

  • File: build.gradle.kts
  • Changes:
    • Added alias(libs.plugins.kotlin.jvm) to the plugins block.
    • Added implementation(libs.kotlin.stdlib) to the dependencies block (though the plugin often adds this automatically, it's good practice to be explicit).

2. Implementing Kotlin Logic

Create Kotlin File (Hello.kt)

We created a new Kotlin file containing basic syntax examples: a function with a return value, a function that prints a sum, and a greeting function.

package learn_kotlin

fun sum(a: Int, b: Int): Int {
    return a + b
}

fun printSum(a: Int, b: Int) {
    println("sum of $a and $b is ${a + b}")
}

fun getGreeting(): String {
    return "Hello from Kotlin!"
}

3. Interoperability

Call Kotlin from Java (App.java)

Finally, we updated the Java main method to call the Kotlin functions. In Kotlin, top-level functions are compiled into a class named after the file with a Kt suffix (e.g., HelloKt).

  • File: App.java
  • Changes:
    • Called HelloKt.getGreeting().
    • Called HelloKt.printSum(10, 20).
    • Called HelloKt.sum(5, 7) and printed the result.

4. Verification

We verified the changes by running a Gradle build: - Ran ./gradlew :app:assemble to ensure everything compiles correctly. - The IDE correctly resolved the HelloKt class after the build/sync.

Comments

Popular posts from this blog

Mastering Per-App Language Preferences: From Android 10 to Android 13+

  One of the most requested features by users is the ability to use an app in a language different from the system language. While Android 13 (API 33) introduced "Per-App Language" settings at the system level, implementing this backward-compatibly for older devices like Android 10 (API 29) used to be a challenge involving manual configuration wrapping. Today, thanks to AppCompat 1.6.0+ , we have a unified, standard way to handle this. Here is the modern guide to implementing seamless language switching. The Architecture: How it Works On Android 13 and above, the system handles the storage and application of your app's locale. On older versions, the AppCompat library manages this behavior by storing your preference in an internal XML file and injecting the resources during the activity lifecycle. Step 1: The Locale Helper Utility Instead of scattering logic across your app, use a clean LocaleHelper object. This handles the distinction between the system LocaleManager (...

Beyond Scanning: Meet the All-in-One AI Document Assistant by Digitify Vision Technology

In an era where efficiency is the ultimate currency, information is scattered everywhere—on physical paper, within QR codes, and inside lengthy digital documents. The challenge isn't just capturing this data; it’s making it work for you. At Digitify Vision Technology , we believe your smartphone should be more than just a camera—it should be a high-performance engine for your daily workflow. Today, we are proud to unveil our most powerful update yet: a total evolution in AI-driven document management. 💡 Key Features of the New Update We’ve bridged the gap between physical information and digital action by integrating advanced vision and audio intelligence into a single, seamless experience. 🔍 Precision Scanning for Everything Our advanced vision engine is now more versatile than ever. Intelligent Document Scanning: Capture crisp, professional-grade scans of physical papers, contracts, or handwritten notes. QR Code Extraction: Instantly scan any QR code to extract text, read URL...
  Optimising Android Launch: Mastering App Startup & The Modern Splash Screen The first few seconds of an app’s life determine a user's first impression. A slow start or a flickering white screen can lead to immediate uninstalls. In this guide, we’ll look at how to streamline your initialisation using the App Startup Library and ensure a seamless visual transition with the Android 12 Splash Screen API (with full backward compatibility for API 29). Part 1: The App Startup Library Traditionally, apps initialised multiple components using separate content providers. This adds overhead and slows down launch time. The Jetpack App Startup library allows all components to share a single content provider, significantly improving performance. Why use it? Performance: Shared content provider reduces overhead. Order: Explicitly set the initialisation sequence. Simplicity: Both library creators and app developers use a unified interface. Part 2: The Modern Splash Screen API Starting ...