Skip to content
DT Nova

Mobile app development with Java: what still works in 2026

Mobile app development with Java is still possible, and many Android apps in the stores are written in it. But the platform around it has changed. Google has made Android development Kotlin-first, its modern interface toolkit is Kotlin-only, and Java has never been a native language for the iPhone. This guide explains what Java can and cannot do on mobile today, the options for iOS, and how to decide whether to build, keep or move a Java app.

It is written for companies weighing Java for Android app development, teams with Java skills or an existing Java app, and for anyone weighing Java mobile app development against the alternatives. For a comparison of every framework, see our guide to mobile app development frameworks.

The short version

  • Java is fully supported for Android's platform APIs, Android Studio and AndroidX libraries.
  • Jetpack Compose, Kotlin Multiplatform and Kotlin-specific libraries are not available from Java.
  • For a new Android app, Kotlin is the better start; for an existing Java app, add Kotlin gradually.
  • Java does not build iPhone apps directly; translation tools and commercial toolkits exist, but cross-platform frameworks are usually more practical.
  • Java skills transfer well: Kotlin runs on the same platform, and backends in Java serve mobile apps of any kind. Java is not JavaScript; for apps written in JavaScript, see JavaScript mobile app development.

Where Java stands on Android

Java was the original language of Android, and it is still supported. Android's page on its Kotlin-first approach (last updated 22 September 2026, read 11 November 2026) states that at Google I/O 2019 Google announced that Android development will be increasingly Kotlin-first, and that when building new tools and content, such as Jetpack libraries, samples, documentation and training, it designs them with Kotlin users in mind while continuing to support using its APIs from the Java programming language. The same page sets out what that means in practice:

AreaJavaKotlin
Platform SDK, Android Studio, lintYesYes
Guided docs and API docsYesYes
AndroidX librariesYesYes
Kotlin-specific AndroidX APIs (KTX, coroutines)Not applicableYes
Online training and samplesBest effortYes
Multiplatform projectsNoYes
Jetpack ComposeNoYes
Compiler pluginsNoYes

The row that matters most is Jetpack Compose. Android describes Compose as its recommended modern toolkit for building native interfaces, and it is written and used in Kotlin. A Java app keeps using the older View system with XML layouts, which still works and is still supported, but new interface features, samples and design guidance increasingly assume Compose.

The same page states that Kotlin is 100% interoperable with Java, so a project can contain as little or as much Kotlin as you want. That is the key fact for anyone with a Java codebase: the decision is not all or nothing.

Which Java Android supports

Android apps are not run on a standard Java virtual machine; the compiled code is converted to Android's own format, and the Java language level an app can use depends on Android's build tools. Android's documentation on Java language features (read 11 November 2026) explains that the Android Gradle plugin implements newer language features by transforming bytecode, a process it calls desugaring, during compilation. With the Android Gradle plugin 4.0.0 or higher, a number of Java 8 language APIs are available without a minimum Android version, and with plugin 7.4.0 or higher and the desugared library 2.0.0 or higher, a number of Java 11 language APIs are available as well.

On the server, Java moves on a different schedule. Oracle's Java SE support roadmap (updated 20 October 2026, read 11 November 2026) lists Java SE 8, 11, 17, 21 and 25 as long-term support releases and the next planned one as Java 29 in September 2027. So a company can run its backend on a current long-term Java release while its Android app uses the subset of the language the Android tools support. Teams moving between the two should know which features they can use where.

Java for iPhone apps

Apple's tools build apps in Swift and Objective-C, and Java is not one of them. Three kinds of route exist for Java code on the iPhone:

  • Translating the logic. J2ObjC is an open-source command-line tool from Google that translates Java source code to Objective-C for iOS, so that an app's non-interface code, such as business logic and data models, can be shared. Its README (read 11 November 2026) states that it provides no platform-independent interface toolkit and has no plans to, that the iOS interface needs to be written with Apple's own SDK, and that it is currently beta quality.
  • Compiling Java for iOS. Commercial toolkits, such as Gluon and Codename One, compile Java applications ahead of time for iOS and Android. They suit teams committed to Java everywhere, at the price of a smaller ecosystem and one more vendor to depend on.
  • Moving to Kotlin Multiplatform. Kotlin Multiplatform shares logic and data code between Android and iOS, while each platform keeps a native interface or shares one with Compose Multiplatform. For a Java team it is the closest step, because Kotlin runs on the same platform and reads familiar to Java programmers.

For most companies whose goal is simply an app on both iPhone and Android, the practical answer is one of the established cross-platform app development frameworks, with the Java skills put to work on the backend that serves the app.

How common Java still is

Java remains one of the most used languages. In the Stack Overflow survey 2025 (read 11 November 2026), 29.4% of all respondents said they had used Java in the past year, against 10.8% for Kotlin; among professional respondents the figures were 29.6% and 11.5%. Most of that Java is server-side and enterprise software, not mobile. The numbers explain why many companies have Java skills in-house, and why using them for the backend while the app uses a mobile-first language is a common arrangement.

Java mobile app development: build, keep or move?

Your situationUsual recommendation
New Android-only app, team knows JavaStart in Kotlin with Jetpack Compose; the Java knowledge carries over
Existing Java Android app that worksKeep it; write new features in Kotlin and move screens to Compose when they are redesigned
Existing Java app that needs an iPhone versionShare logic with Kotlin Multiplatform, or rebuild the app in a cross-platform framework if the interface is due for redesign anyway
Backend in Java, new app for both platformsKeep the backend in Java; build the app cross-platform or native, connected through an API
Old Java app with a poor structure and frequent crashesA planned rebuild, screen by screen, with the old app kept live until the new one replaces it

Whatever the path, the stores' yearly requirements apply to Java apps too. Google Play's target API level rules and the Play Billing Library's deprecation cycle mean an untouched Java app falls out of date within a year or two; our mobile app maintenance page lists the current dates.

Moving a Java app to Kotlin step by step

  1. Set the rule. New code in Kotlin from a fixed date; existing Java stays until it needs changing.
  2. Start at the edges. Tests, small utilities and new screens are the low-risk places to introduce Kotlin.
  3. Move screens to Compose with redesigns. Compose and Views can live in the same app, so screens move one at a time.
  4. Convert core classes last. Data models and business logic are converted when they are touched for other reasons, with tests in place first.
  5. Keep releasing. The app goes out to users throughout; there is no long branch that never ships to the stores.

How DT Nova helps

We maintain and extend Android apps written in Java, add Kotlin and Jetpack Compose where they pay back, and build the iPhone version when one is needed, choosing between Kotlin Multiplatform and a cross-platform framework with you in a written scope. For Android-only work, see Android app development; for the wider picture, mobile app development. The code sits in your repository and the apps are published under your company's accounts, with any backend we add hosted in an EU region.

Questions people ask

Can you still build Android apps in Java?

Yes. Android's own Kotlin-first page lists Java support for the platform SDK, Android Studio, lint, guided and API docs and AndroidX, and Google states it continues to support using its APIs from Java. What Java does not get is Jetpack Compose, Kotlin-specific AndroidX APIs, multiplatform projects and compiler plugins; samples and online training for Java are best effort.

Is Java or Kotlin better for Android?

For a new Android app, Kotlin. Google has called Android development Kotlin-first since Google I/O 2019, its modern interface toolkit Jetpack Compose is Kotlin-only, and new samples and libraries are designed for Kotlin users. Java remains a sound choice for maintaining an existing app, and the two languages work in the same project.

Can Java be used to build iPhone apps?

Not directly in the way Apple's own tools work. Options exist: Google's J2ObjC translates Java business logic to Objective-C but provides no interface toolkit and is described by its authors as beta quality, and commercial toolkits compile Java for iOS. For most companies, Kotlin Multiplatform or a cross-platform framework is the more practical route to an iPhone app.

Which Java version can an Android app use?

Android does not run the latest Java directly. The Android Gradle plugin supports Java 8 language features through desugaring, and with plugin 7.4.0 or higher and the desugared library 2.0.0 or higher a number of Java 11 language APIs are available on older devices too. The usable language level depends on the plugin version and the app's minimum Android version.

Should we rewrite our Java Android app in Kotlin?

Rarely all at once. Kotlin is fully interoperable with Java, so the usual path is to write new features in Kotlin, move screens to Jetpack Compose as they are redesigned, and leave stable Java code alone until it needs changing. A full rewrite is justified only when the old code is also the problem.

Sources