What "mobile app" means when you build one with Anticode
"Mobile app" can mean three different things: a website that works well on a phone, a web app installed on the home screen, or a native app from the App Store or Google Play. Anticode builds the first two directly and gives you a starting project for the third, which you submit yourself. This page explains the difference and what each can and can't do.
Three kinds of mobile app
| Mobile web app | Installed web app (PWA) | Store app | |
|---|---|---|---|
| How people get it | Open a link | Open a link, then add to home screen | Download from a store |
| Icon on the home screen | No | Yes | Yes |
| Works offline | Only what's loaded | With an offline fallback | Depends on the app |
| Store review | None | None | Required, per store |
| Updates | Instant | Instant | Through the store, or instant if it loads web content |
| Device features | What the browser allows | What the browser allows | Native APIs, if a developer adds them |
For a tracker, a calculator, a game or a booking tool, the installed web app is often all you need: it opens from an icon, runs full screen and needs no store approval. A store listing matters when your audience expects to search for you there, or when you need native device features.
What Anticode builds
Describe the app as you'd describe it to a developer, with the phone in mind: "A dog-walking log for one owner: start and stop a walk with a big button, a list of past walks with duration, a weekly chart, notes per walk. Designed for one hand, bottom navigation, dark theme." The model writes it as one HTML, CSS and JavaScript app, designed to work from a phone screen up to a desktop. When the review service is available, new app builds are opened in headless Chrome at phone and laptop widths, screenshotted and clicked through, and the problems found are fixed before you see the result.
Installable on any phone
Every site you publish with Anticode has a web app manifest and icons, so it can be installed on phones and desktops, with an offline fallback. On Android, browsers offer to install it; on iPhone, people use Share, then Add to Home Screen. Tell users how on your first screen, because many have never done it.
A project for the App Store and Google Play
For store distribution, Anticode gives you two things: a checklist of what the stores will ask for, and a Capacitor project for iOS and Android to download. Capacitor puts a web app inside native iOS and Android shells. You open those in Xcode and Android Studio, sign them with your own developer accounts and submit them. Submitting to the stores is up to you; Anticode doesn't talk to Apple or Google on your behalf. See app-store packaging.
Store review is a real hurdle for wrapped web apps. Apple's App Review Guidelines expect an app to offer more than a repackaged website, so a thin wrapper around a marketing page is likely to be rejected; an app with genuine, app-like functionality has a better chance (Apple's guidelines, section 4.2). Google Play has its own policies. Read both before you plan a store launch.
Native features that are out of reach
Anticode apps run in a strict browser sandbox. Beyond having no network, they don't ask for device permissions. That rules out:
- Camera and microphone: no scanning, photo capture or voice notes.
- Location: no GPS tracking of runs or walks, no "near me".
- Push notifications: the app can't alert you when it's closed.
- Contacts, calendar, health data, Bluetooth, NFC: none of these are available.
- Accounts and sync: data saves in that phone's browser only, so a second device starts empty.
- In-app purchases and payments inside the app.
A developer working in the Capacitor project could add native plugins for some of these, but at that point it's a software project of its own, outside the sandbox and outside what Anticode builds and checks.
When to use a different tool
If your app's core depends on the camera, location, notifications or data shared between users (a delivery app, a social app, a fitness tracker that records GPS routes), an AI mobile app builder that produces native code, or a developer working in React Native or Flutter, is the better fit. For a multi-user product on the web, Anticode's Next.js export is a starting point with a database and sign-in. Anticode suits apps that do their job on one phone: logs, calculators, games, quizzes, checklists, planners.
Questions people ask
Can I build a mobile app with AI and put it in the App Store using Anticode?
You can download a Capacitor project of your published app and submit it yourself with an Apple developer account. Whether it's approved depends on Apple's review.
Do I need a Mac?
Building and submitting the iOS version with Xcode needs a Mac. The Android version can be built in Android Studio on Windows, macOS or Linux.
Will updates reach installed users?
For the installed web app, yes: it loads your latest published version. For store builds, it depends on how the Capacitor project is configured; check before you submit.