# Does Cursor Generate Accessible Android Apps?

DevFeed: [Does Cursor Generate Accessible Android Apps?](<https://devfeed.tech/articles/does-cursor-generate-accessible-android-apps-38507.md>)

Original publisher: [Read original article](<https://eevis.codes/blog/2025-06-16/does-cursor-generate-accessible-android-apps/>)

Author: Eevis Panula

Published: 2025-06-16T03:56:47.185000Z

Content type: article

Language: en

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

Topics: [cursor](<https://devfeed.tech/topics/cursor.md>), [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [android-development](<https://devfeed.tech/topics/android-development.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

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

## AI overview

The article evaluates Cursor for generating an Android app and testing its accessibility. In one test, the author used Android Studio and Cursor to build a yarn and knitting-needle tracking app, encountering missing dependencies, improper navigation, and non-existent parameters in Composable functions. The author preferred Gemini and Junie for Android development based on this experience.

## Source excerpt

I've been testing the accessibility of Android code created by different AI tools, and this time, it's time to test Cursor. I know it's not the most ideal tool for Android development, but I still wanted to test it. If you've read the previous posts in the series, you know the drill - I'll generate the app code and then test it. There are links to the blog post at the top of this post if you want to refresh your memory or if you haven't read the previous blog posts. In them, I also explain why I'm doing this. So, let's get to the actual thing we're here for. The App This time, I did only one round of tests. It's not that I got lazy or anything - using Cursor was just so annoying that I decided to do only one test. I used a combination of Android Studio and Cursor editor to construct the app. I created the project with Android Studio, opened it in Cursor, and wrote the app prompt. Then I moved to AS, tried to build the project, fixed issues with dependencies, and built it again. Then I realized it didn't have proper navigation, so I moved back to Cursor and did some additional prompting. After several similar rounds, I finally got the app to my phone and the testing phase. There were some good and not-so-great sides to using Cursor from an Android development point of view. The setup was smooth, but once I got to do some actual work with Android, the code had many problems. For example, it didn't add dependencies at all, and I had to add them by hand. It also added some non-existent parameters to Composable functions. So yeah, compared to Gemini and Junie (tools I've tested so far), I would go with either of those for Android development instead of Cursor. Prompt The prompt I gave to Cursor was: Can you generate UI screens for an app, in which user can keep track of their yarn stash and knitting needles per size and type? It should contain the following screens: Home screen, where user can add both yarn and needles, a list screen for yarn, a details screen for indivi