Meta just shipped a vibe-coded app to the App Store. Vibe coding isn't a hobbyist story anymore.
Meta quietly launched Pocket, a consumer app built on its Gizmo acquisition that lets anyone generate small playable games — 'gizmos' — from a text prompt, no code involved. When a company Meta's size ships prompt-generated software to production, the debate about whether AI-built apps are 'real' is effectively over.
6 July 2026
Meta quietly launched Pocket on the App Store and Google Play on 29 June, without an official announcement. It’s a creative platform for making and sharing “gizmos” — small interactive games and apps generated from a text prompt — built on the team Meta acquired from vibe-coding platform Gizmo earlier this year. Users scroll a feed of gizmos other people made and can remix or build their own with no coding involved.
Why a quiet launch from Meta is the real signal
Vibe coding has spent the last two years as a story about solo founders and weekend prototypes. Pocket is different: it’s a production consumer app, shipped by one of the largest software companies in the world, built entirely on prompt-generated content as the product itself rather than a scaffold a developer then rewrites. Meta didn’t build Pocket to prove a point about AI — they built it because the economics and the output quality finally justified shipping it to hundreds of millions of users. That’s a different signal than another startup’s funding round.
The catch that still applies
Nothing about Pocket contradicts what we’ve said before about AI-generated software: it works well for small, contained, disposable experiences where a bug means a bad game, not a bad transaction. Games and gizmos tolerate imperfection in a way that a checkout flow, a patient record, or an appointment booking system does not. Meta shipping this doesn’t mean the same prompt-to-production pipeline is safe for a regulated, revenue-critical, or data-sensitive product — it means the bar for what AI-generated software is trusted with just moved, and founders evaluating “should we just vibe-code our MVP” now have a genuine Big Tech data point to weigh, not just anecdotes.
So what
If you’re deciding whether a prompt-built prototype is enough or whether you need an engineered product, the honest answer depends on what happens when it’s wrong — not on whether the technology can generate it. Our custom software development page covers where we draw that line in practice, and get in touch if you want a straight read on your specific case.