Vibe Code Forum teamAdmin
Who it suits: people whose idea needs to live on a phone: camera, notifications, offline use, or a place in the app stores.
First, do you need a store app?
A web app that works well on a phone can be saved to the home screen and covers many ideas, with none of the store reviews or fees. Build that first if you can. Choose a store app when you need things the web does poorly, or when being in the store matters to your users.
The common routes
- React Native with Expo: one JavaScript codebase for iOS and Android. AI tools know it well, and the Expo Go app lets you run your work on your own phone by scanning a QR code while you build. Some AI app builders can create Expo apps directly.
- Flutter: Google's toolkit, with visual builders such as FlutterFlow on top.
- Native (Swift for iOS, Kotlin for Android): the most control, the most to learn. Fine with an AI editor if you only need one platform.
How to start (Expo route)
- Set up an AI code editor or terminal agent, plus Node.js.
- Ask: "Create a new Expo app with one screen that shows a list I can add items to. Tell me how to run it on my phone with Expo Go."
- Install Expo Go on your phone and scan the code. Seeing your app on your own phone in minutes is very motivating.
- Grow it one screen at a time, testing on the phone after each change.
Getting into the stores
- Apple requires a paid developer account (yearly) and reviews every app. Google Play has a one-off registration fee and its own review.
- Expo's build service (EAS) can build store-ready apps without owning a Mac, which matters for iOS.
- You need an icon, screenshots, a privacy policy and honest answers about what data you collect.
Watch out for
- Store rules on payments and privacy are strict; read them before building features that sell things.
- Test on a real device, not only a simulator.
- Keep API keys off the phone: anything inside an app can be extracted. Put secret work on a server.