We hosted a live AMA on r/GoodBarber, opening the floor to any question about publishing an app on the App Store — App Review, App Store Connect, developer accounts, all of it. The answers came directly from the support team that handles App Store and Google Play submissions every day, with iOS engineers pulled in whenever a question got technical. Here's the recap. We get this question a lot, so we looked at our own support cases from the last 18 months. The most common rejection reasons are less dramatic than people expect:Incomplete or inaccurate App Store metadata — missing or misleading information, screenshots, descriptions.An incorrectly configured App Privacy form.Apps that Apple considers incomplete or not fully functional during review.Beyond that, we regularly see rejections tied to content rights (especially audio or video), apps in regulated industries that don't meet Apple's expectations, or apps judged too close to something that already exists.For a first-time submission, it starts with the metadata: highlight your app's real value instead of generic promotion, and follow Apple's guidelines — they're the baseline for everything else. And if you do get rejected, don't panic. A rejection isn't a dead end, it's usually just part of the process. Read Apple's feedback carefully, address each point, and resubmit — we've seen plenty of apps get approved after one, or several, rounds of review.If you're convinced a reviewer got it wrong, stay factual. Explain clearly why you believe your app complies with the guideline in question, and back it up with whatever helps — screenshots, a screen recording, test credentials, step-by-step instructions if a feature isn't obvious. If the discussion stalls, you can request a call with an Apple representative through the App Resolution Center in App Store Connect — a direct conversation often clears up misunderstandings faster than a written back-and-forth. As a last resort, you can appeal to the App Review Board, where a senior member of Apple's team reviews the case. Either way, the goal isn't to prove Apple wrong — it's to make it as easy as possible for the reviewer to see why your app complies.

On February 2, 2025, Andrej Karpathy named the thing: “There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.” Nine months later, “vibe coding” was Collins Dictionary's Word of the Year. Few tech terms have traveled that fast — because few tech experiences are that intoxicating.The numbers say the same. Lovable reached $100M in annual recurring revenue eight months after launch, with more than 10 million projects created on the platform. Bolt.new reached roughly $40M ARR in about five months. Replit multiplied its revenue tenfold in half a year after launching its agent. Millions of people typed a sentence and watched software appear.We understand the high. It's the same one our users feel when they describe a feature and see it running in their app. Seeing your idea work — not mocked up, working — changes what you believe you can build. That part deserves no irony.But Karpathy put the caveat in the very same post: vibe coding is “not too bad for throwaway weekend projects.” The people living it say it with less restraint. One builder on r/nocode titled his post “Tried Bolt.new. Felt Like a God. Then Reality Slapped Me.” and summed up the morning after: “Suddenly, the dream of 'AI-powered coding' turned into 'AI-powered anxiety.'”The demo isn't a lie. The mistake is reading it as a finished product.

Short answer: yes — with one honest caveat. We handed GoodBarber's AI Extension Builder a deliberately unfair brief — build Flappy Bird, full-screen, with a leaderboard shared across every player — and it delivered, from a single prompt, no code. Here's the result, the exact prompt behind it, and what this proof of concept really says about no-code. A video game isn't what you'd expect from an app builder.That's exactly what makes it a good test. To find out what the AI Extension Builder is really capable of, you're better off asking it for the improbable than for one more section. So we described a full arcade game — finger-tappable, full-screen, a leaderboard shared across every player — and watched to see how far it would hold up.It held up. The lesson isn't "go publish games," it's "the ceiling is far higher than you think": what's true for a Flappy Bird is true for the sharp, specific feature your app actually needs. Everything was described in plain language, in a few paragraphs. Here's the result.

This month's updates focus on visibility, compliance, and user experience — new ways to highlight key actions, protect younger users, and smooth out everyday interactions in your app. Here's what's new: New global Floating Button: highlight a key action across your whole app, configured once from the Structure panel. Age Protection: a new feature to comply with regional age-verification laws and automatically protect younger users. Event map thumbnails: events shown on a map can now appear as their own thumbnail image instead of a standard pin, so each one is instantly recognizable. Show/hide password: your users can now tap the eye icon to show or hide their password on any login or sign-up screen, so a typo never blocks them again.