Open Apped on your phone, describe an app in a chat, and a coding agent writes it for you in React Native. It bundles the project and hot-loads it into the Apped shell on your phone. You tap Preview and use the app a minute later.
To change something, you open the chat again and say what’s wrong. To take the app out of Apped, Max lets you download the whole Expo project from the dashboard. It’s a standard TypeScript workspace. Nothing about it will surprise a developer.
Most things that call themselves “AI app builders” make a web page and ask you to add it to your home screen. That’s fine for some ideas. It is not what Apped does.
When you describe an app to Apped, it writes a React Native project in TypeScript, pulls in whichever native modules are needed, bundles the code with Babel, and hot-loads it into the Apped shell on your phone. That’s the same stack behind a lot of apps you already pay for in the App Store: React Native with Expo. The animations are native animations, the camera is the camera, and the code that runs is the code you see in the chat.
You can live inside Apped and keep editing by message. That’s the workflow most people settle into. Or, on the Max plan, download the whole project from the dashboard as a zip and open it in Cursor, VS Code, or Xcode. It’s a standard Expo workspace (TypeScript, package.json, the works). You bring your own Apple Developer account and EAS credentials to ship it to the App Store.
These are the kinds of apps the agent tends to get right on the first prompt. Copy one into the chat and it’ll have a runnable first version on your phone in about a minute.
Anything where you log a thing about yourself every day. The data lives on the phone (MMKV), so there are no accounts, no syncing, nothing to sign up for.
Structured content you browse, search, and come back to. Store it on-device with MMKV or SQLite, or back it with a small Hono + Drizzle server if you need it on more than one phone.
Small apps built around a single device capability: camera, maps, haptics, push notifications, contacts, calendars, sensors.
Reanimated and Skia are in the toolbox, so you can get a surprisingly long way on simple single-player stuff.
Anything that needs its own backend, user accounts, shared state between devices, third-party API integrations, or payments is possible but still not reliable enough to call production-ready. Apped can scaffold Hono, Drizzle, SQLite, Zod, and better-auth for simple cases, but you’ll still hit edges.
The chat is where everything happens. As Apped edits files, each tool call streams into the conversation so you can follow the reasoning. Your preview is always one tap away. Open it, tap around, then pull the chat back up to iterate.
Every message and every file version is stored. You can scroll back through the full conversation and see what the agent did and when. If it breaks something, explaining what went wrong in the chat is usually the quickest way forward.
Any app you’ve built can be shared with a public link. Other Apped users can open it and remix it, which forks the whole project into their account. People who don’t have Apped yet land on a branded preview page with a download link.
On Max, the dashboard at apped.dev gives you a zip of the project: standard TypeScript, package.json, app.config.ts, a README. Open it in Cursor, VS Code, or Xcode. You add your own EAS credentials and Apple team ID to ship it yourself.
Apped can reach for any of these on the phone or in the sandboxed server runtime without pulling from npm or asking you to run anything. They come typed and wired up so the agent can import them mid-write.
Credits reset weekly. Paid plans are billed weekly. Max adds export access. No seats, no upsells, no phone calls to sales. There is no sales.
Subscriptions are purchased with RevenueCat and mirrored back onto your Apped account. Cancel anytime from your Apple ID subscriptions.
I’ve been running Apped as a closed beta for months, and there are edges I know will bite you. Rather than hide them, here’s the list. If any of these are deal-breakers for your idea, save yourself the download.
Android is on the waitlist below. The React Native code the agent writes is cross-platform in theory, but the over-the-air preview pipeline and App Store submission path are iOS-only today.
If your app needs logins or state across devices, the agent can now scaffold a little Bun backend with Hono, Drizzle, SQLite, Zod, and better-auth. It works for simple cases. For anything production-shaped, I'd export the project and replace that layer with something you own.
Public APIs work fine from inside the app. Anything that needs a secret (Stripe, a private OpenAI key, a custom backend token) doesn’t have a secure home yet. The workable path today is to export on Max and wire the key into your own build, outside the Apped shell.
Apped serves a live bundle into its own shell while you’re building. If you want the app in the App Store as its own icon, you export on Max and take it through EAS and App Store Connect yourself. I want to make that part easier; it isn’t there yet.
No collaborative editing, no comments, no multi-author projects. It’s a tool for one person thinking at the phone.
I’m Jasper. I’ve been writing React Native for a long time and I got sick of the gap between “I have an idea in my head” and “it’s running on my phone.” Apped is the shortest line I could draw between those two points. It’s not a company yet. It’s me, a laptop, a bunch of build servers, and a probably unhealthy number of hours.
If you find a bug, or something obvious is missing, or just off, email me at support@apped.dev. I read everything and I ship fixes most weeks. If the idea of buying a tool from one person makes you nervous, I understand. But that’s also the reason Apped can be opinionated about what it does and doesn’t try to be.
The first one takes about a minute. The second takes less, because you already have the idea.
The agent already emits cross-platform code. The build and install pipeline is what’s missing. Drop your email and I’ll send one message when it’s ready.