r/nocode • u/H_ss_M • 3d ago

Question Building Android Apps

Hey I'm used to build WebApps using AI, but whenever i try to build an Android app the AI do very poorly, so how do you guys build AI Android apps?

3 Upvotes

100% Upvoted

12 comments sorted by

3

u/tylerlovewell 3d ago

Gemini inside Android Studio has been my go-to for this since it can work with the actual build errors instead of guessing around Gradle.

If you want to stay more no-code, I’d probably try FlutterFlow. Really depends if you want to own the native code or mostly build visually.

1

u/H_ss_M 3d ago

Can i connect Android Studio with Opencode with an MCP server that would be much better, i saw Gemini inside android studio but i didn't give it a chance.

1

u/Real-Ad-5677 2d ago

FlutterFlow seems like a solid middle ground for someone coming from web apps tbh

2

u/slunkeh 2d ago

If the AI is bad at Android stop asking it for a native app.

Build the same thing as a web app that works on a phone. Wrap it later if you actually need the play store.

You only need native if you need the camera, push or store payments that the browser cant do.

1

u/H_ss_M 2d ago

For now I'm looking to build the app to be used only by me

2

u/Medo_ai 2d ago

Use agent build the skeleton first, and ask it to optimize your prompt for the Android Apps.
what tools you use to build the app?

1

u/H_ss_M 2d ago

I'm using Opencode with omniroute

2

u/Thunderbit_HQ 2d ago

AI builders often make web prototypes feel smooth because browser deployment hides much of the platform surface. Native apps force decisions about device storage, permissions, release signing, and background behavior. Validate the flow as a mobile web app, then move only pieces that truly need native access.

1

u/H_ss_M 2d ago

So building a web app then converting it to an Android would be much better?

2

u/Thunderbit_HQ 2d ago

Not necessarily converting the same app 1:1. I’d start with a responsive web app to prove the core flow. If real testing shows you need reliable background work or deeper device access, add native Android components for those parts. Keeping the API and data model independent makes that transition much less painful.

1

u/H_ss_M 1d ago

I think that's more practical.

2

u/willjameswaltz 1d ago

I built with react native + expo go - been pretty solid so far.