# Does Junie Create Accessible Android Apps?

DevFeed: [Does Junie Create Accessible Android Apps?](<https://devfeed.tech/articles/does-junie-create-accessible-android-apps-38506.md>)

Original publisher: [Read original article](<https://eevis.codes/blog/2025-05-10/does-junie-create-accessible-android-apps/>)

Author: Eevis Panula

Published: 2025-06-10T04:54:16.242000Z

Content type: opinion

Language: en

Sources: [Eevis Blog](<https://devfeed.tech/sources/eevis-blog.md>)

Topics: [junie](<https://devfeed.tech/topics/junie.md>), [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Android](<https://devfeed.tech/topics/android.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>)

Tags: [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [junie](<https://devfeed.tech/tags/junie.md>)

## AI overview

The article reports on two rounds of testing Junie, JetBrains' coding agent, by generating Android apps and evaluating their accessibility. It also discusses Junie's structured workflow, unnecessary library additions, a KSP version issue, and differences between its Early Access and generally available versions.

## Source excerpt

I'm continuing my tests with AI-generated Android code and how accessible these generated apps are. This time, the tool of choice is Junie, the coding agent by JetBrains. If you want to know why I'm doing this or want to read my take on how accessible code Gemini creates, the first post is available at Does Gemini Create Accessible Android Apps?. So, I got into the Early Access Program (EAP) before Junie was generally available and generated the first app. I had all these plans to proceed to the second run and write this blog post sooner, but then life happened, and I founded my own company. Suddenly, time passed, and Junie is now generally available. Before we dive into the application generation and accessibility testing, I'll share a couple of words about Junie I wrote right after the first try, with some additions after the second run. Junie As mentioned, I got access to EAP and was curious to try Junie out, as it differed from the AI solutions for coding I'd used before. Particularly, it also changed the files and didn't just give me the code, and I could skip all the hard work of creating files and copy-pasting the code into those files. Some thoughts I had: I was impressed by the structured approach for doing things. It was easy to follow what was happening next and what was coming after that. When creating the first app, Junie kind of went overboard with adding libraries like Room into the project, but not using them in the code. With the first app, I had to solve one KSP version issue by hand, because I got tired of Junie trying to find a working library version. It used some non-existent version numbers first. The second app used kapt, which resolved the version right away. I had to iterate a bit with the first version to get all the features I wanted, like adding yarn. The second app generation was smooth from this point of view. The App As with the tests with Gemini, I did two rounds of testing - first, with the Early Access Program version back at the b