The short list
| Tool | Output | Play-ready? | Free tier |
|---|---|---|---|
| ShipNative | React Native + Expo | ✅ AAB via one command | ✅ |
| FlutterFlow | Flutter | ✅ | ✅ |
| Google AI Studio (app builder) | Android-leaning web/experiments | ⚠️ Early | ✅ |
| Cursor / Claude Code | Kotlin, RN, anything | You do the work | ⚠️ |
| Glide | PWA | ❌ No store listing | ✅ |
1. ShipNative, prompt to Play-ready app. Describe the app, get a React Native + Expo project with screens, navigation, auth, and database. Android specifics handled: eas build --platform android outputs a signed AAB with managed keystore, the two things (signing, bundling) that most reliably wreck first-time Android publishers. Cross-platform bonus: the same project ships to iOS. Free to build and preview.
2. FlutterFlow, visual + AI, strong Android pedigree.Flutter is Google’s own framework; rendering consistency across cheap Android hardware is its signature strength. Choose it if pixel control across low-end devices matters more than the React ecosystem.
3. Google AI Studio, free and improving fast.Google’s build-an-app flow generates working projects free, with Gemini underneath. Today it’s best for experiments and simple utilities; the production path (signing, store pipeline, iOS) is still yours to assemble. Watch this one.
4. Cursor / Claude Code, for developers. Kotlin or React Native, full control, zero guardrails. Right if you already handle Gradle errors calmly.
5. Glide, internal Android “apps.” Spreadsheet-driven PWAs installed via browser. Fine for a team tool; invisible on the Play Store.
Android-specific reality check
Whatever tool you pick: budget for the Play Store’s closed-testing requirement (12 testers, 14 days for personal accounts, see the full publish guide), test on at least one cheap device (emulators lie about jank), and prefer tools that manage your signing keystore, losing one is unrecoverable.
Start free
Generate your Android app free at shipnative.dev: AAB-ready when you are.