Yes, for a large and useful class of apps, and you can verify it in an afternoon for free. We host AI-built apps, which means we watch strangers with no coding background describe software and receive it. This is the honest map of what that looks like, including the parts that fail.
What "for me" actually means now
The current generation of tools is not a code snippet generator you have to assemble. A coding agent takes your description, writes the full application (files, server, database), deploys it to a live URL, and then keeps modifying it as you ask in plain language. The loop is: say what you want, look at the live page, say what to change.
In the last few weeks alone, real people on our platform, mostly non-developers, shipped booking systems for local businesses, fantasy sports league managers, daily planners with meal and shopping features, persistent browser games, online course portals with quizzes and admin dashboards, and small storefronts with order management. None of those started from a template that happened to match; the agent built each shape to order.
Where it reliably works
The pattern behind those successes: apps whose logic you can describe in sentences. Booking, scheduling, tracking, membership, catalogs, forms, dashboards, games with stateable rules. If you can explain the app to a smart assistant over the phone, an agent can usually build it, and the first working version typically lands in the first message or two.
The three places projects actually fail
We read the transcripts of builds that stall. It is almost never "the AI could not write the code." It is one of these:
1. The exact-look trap. "Make it look exactly like this screenshot" is the hardest request in the category. Agents get you a clean, professional look easily and a pixel-perfect replica of a reference painfully, if at all. If your requirement is a specific existing design down to the pixel, budget patience.
2. The services only you can sign up for. Taking real payments needs a Stripe account and its secret key. Sending email needs an email provider. Texting needs Twilio. The agent wires all of this competently, but it cannot create the accounts, and a surprising number of stalled projects are simply waiting on a key only the owner can fetch. Plan for twenty minutes of account setup when your app touches money or messages.
3. Vague iteration. "Make it better" produces ten rounds of mutual confusion. "Move the sign-out button to the top bar on every page" lands on the first try. The people who get the most out of these tools send one concrete change per message. This is also what keeps costs at pocket change.
What no chat-based tool does end to end
A native App Store app requires an Apple developer account, code signing, and review; every chat builder that claims otherwise is building you a web app, which is usually the right answer anyway, since a mobile-first web app installs to the home screen and feels native. And venture-scale engineering (millions of users, complex integrations, a security team's requirements) still belongs to engineers, who are themselves using these same agents to go faster.
How to find out for your idea, concretely
- Write your app down in five to ten sentences: who uses it, what they see first, what they can do.
- Give that to a builder with a free tier and look at the live URL it produces.
- Spend your next three messages on the one flow that matters most (the booking, the order, the signup), not on colors.
If the core flow works by message five, your idea is in the buildable class, and you learned it for free. VibeKit is our version of this: describe the app, get a live URL, iterate by chat from the web or the iOS app, free tier first.