Dumè Siacci, Tuesday 21 July 2026

Prompt teardown: GPS, memory, and Maps from a single sentence

Nobody doubts anymore that an AI can generate capable code — even "vibe-coded," it works, sometimes very well. That's not the interesting question. The interesting question is: once it's generated, what does that section actually do inside your app? Does it sit in a corner as an isolated block, or does it use what the phone and the app already know how to do? The most honest way to answer is to take a prompt and pull it apart, line by line.That's what this series is for. In each episode, we'll take one prompt from the AI Extension Builder's library and pull it apart: where it trusts the platform, where it overrides it, and what the resulting section can really do. First up, one of the library's example prompts: "where did I park?"Here's the shortest prompt you could write for this:Build a "remember where I parked" helper.That's it. One sentence, not a spec. And here's what comes out:A button to save your location. A section that finds that spot again when you reopen the app. A button to head back to the car. A discreet link to clear it. And if you decline location access, a screen that explains it instead of crashing.The surprise isn't that seven words draw a screen. It's that this section, born from one sentence, already reaches the device: it reads the GPS, it keeps a memory, it opens Maps. We asked for none of those three things.
Elena Debonis, Friday 10 July 2026

App Store publishing: everything you asked at our Reddit AMA

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.
Pierre-Laurent Medori, Friday 10 July 2026

Vibe coding is magic in the demo. Is your app really production-ready?

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.
Mathieu Poli, Monday 6 July 2026

Can a no-code app builder make Flappy Bird? I tried.

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.
Paul-François Simoni, Wednesday 1 July 2026

What's New at GoodBarber? June 2026

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.
Mathieu Poli, Wednesday 1 July 2026

AI Extension Builder: add a Supabase database to your app

The AI Extension Builder already lets you create a custom app section by describing it in plain language. Now those sections can remember and share real data. Ask for a poll, a booking list, or a guestbook, and the builder sets up the data behind it and connects it to your live app — through a new integration with Supabase. Until now, the AI Extension Builder was brilliant at one thing: turning a sentence into a working section. Describe a countdown, a mood board, a mini-game — it appears in your app, styled to fit right in. But every section it built lived entirely on the visitor's device. Nothing it produced could hold on to information or pass it between people.That was the limit. Ask for a "reader poll" and you'd get a poll that worked perfectly for one person, on one device. The votes lived in the browser. Close the app, and they were gone. Open it on another phone, and the count started at zero. A guestbook only you can read isn't a guestbook. A booking list that resets on every device isn't a booking list.The reason was always the same: those features need a place to keep their data, and a set of rules for who can read and write it. That layer — a backend — is the hard part, and it's exactly the kind of thing that used to sit among the limitations of no-code app builders. The new Supabase connector brings it inside the builder. The AI Extension Builder now builds the data layer along with the section, in the same conversation, before it writes a line of code.(If you're new to building sections this way, start with how the AI Extension Builder works — this article picks up from there. It's the same tool that recently learned to handle file uploads, now with a data layer too.)
Dumè Siacci, Tuesday 30 June 2026

AI Extension Builder: upload your own files

When we launched the AI Extension Builder, it could build a custom section from a single prompt. The missing piece was your own material: until now the assistant started from a blank slate, wrote the code, rendered it live — but with its own stand-in images. To use your logo or your data, you had to point to an external URL, a fragile link hosted somewhere else. The new file manager removes that step.Take a running club that wants a "Race calendar" section in its app.The owner opens the Assets panel and drops in two files: logo.png and a races.csv with the dates and locations. Then they ask the assistant:"Show the upcoming races from this CSV, with our logo at the top."The assistant already knows these files. It doesn't invent them, recreate them, or base64-encode them: it references them by their exact URL — logo.png in an <img> tag, races.csv through a fetch(). The section renders live, in the club's colors, with its real dates.Days of work for a developer, minutes here. And the result isn't a mockup: it's a native extension, hosted by GoodBarber, that ships into the published app like any other section.
Elena Debonis, Monday 29 June 2026

AI Extension Builder: everything you asked at our Reddit AMA

Last week we ran an AMA on r/GoodBarber, focused on the AI Extension Builder — the beta feature that turns a plain-language description into a real, integrated section of your app. Better still, the developers who actually built the feature were in the thread, answering directly. The questions were excellent: specific, hands-on, and often from people who'd already built something. Here's what came out of it.A recurring discovery from people testing the builder: more iterations don't automatically mean a better result. Past a point, changes get less relevant — and starting fresh with a clearer prompt often beats endlessly steering an existing one.Our take: iteration works best when you're refining the original intent. When each round changes the direction of the project, it's usually more productive to start over. The quality of that first prompt has an outsized impact — the clearer you are about what you want to build, the expected functionality, and the user experience, the better the output.
Mathieu Poli, Friday 26 June 2026

How to test GoodBarber Custom Code with a logged-in user

A lot of Custom Code needs to know who is using the app right now: showing premium content, greeting members by name, hiding a section from anonymous visitors, adapting a checkout. The GoodBarber App API gives you the current user through gb.user.getCurrent().And Custom Code isn't only something you write by hand anymore. With GoodBarber's AI Extension Builder, you describe the section you want in plain language and the assistant generates the extension for you — code that plugs straight into the same GoodBarber App API. Hand-written or AI-generated, it calls gb.user.getCurrent() the same way, and you test it the same way. So this guide applies whether you typed the code or prompted for it.But here's the catch every developer eventually hits: inside the back-office preview, there is no logged-in user. The preview is just a render of your app — there's no login screen, no session, nothing to authenticate against.For most app types, GoodBarber quietly works around this for you, so testing “as a logged-in user” just works. For the Membership extension, it doesn't — and that's on purpose. This article walks through how the current user behaves in the preview for each app type, and gives you a simple, copy-paste way to test the trickiest case: a logged-in member.
Muriel Santoni, Tuesday 16 June 2026

GoodBarber vs BuildFire

Most app-builder comparisons pit two opposite philosophies against each other: a tool that makes you design a database against one that hands you finished features. GoodBarber and BuildFire are not that comparison. They agree on the method — you configure pre-built features instead of wiring atomic building blocks, and you reach a publishable app fast. That shared starting point is exactly why the decision between them is interesting: when two tools take the same shortcut, the question stops being "which approach" and becomes "what do you actually ship, and how well does it hold up?"To answer that concretely, we ran the same brief through both platforms: AURORA, the test app we use across this whole series.BuildFire is a mature, capable platform with thousands of live apps and a deep plugin catalog. The honest answer is that the two tools fit different operators — and the clearest fault lines run through native output, what's included in the subscription, and the economics of running apps over time.
Mathieu Poli, Tuesday 16 June 2026

World Cup 2026: add a match schedule and results section to your app, no code required

The 2026 World Cup has kicked off, and the matches are about to grab everyone's attention — a chance to keep your audience close and bring in a new one, right inside your app. Here's how to add a a match schedule and results section to it — each match's score, the next match up front, kickoff time in the visitor's local zone — starting from a single prompt, with GoodBarber's AI Extension Builder. From June 11 to July 19, 2026, 48 teams and dozens of matches will set the rhythm for six weeks of worldwide attention. Meanwhile, your community is following the scores on five other apps. None of them carries your name.A fixtures and results section is exactly the kind of page that, until recently, called for a developer. Today, you describe it and it builds itself. Here's how.
Pierre-Laurent Medori, Monday 15 June 2026

Agent-Ready Apps: Why Your App Must Be AI-Operable in 2026

For fifteen years, software raced to be easier for people to operate. That race is ending. The next one is whether your app can be operated by an AI agent at all. Here is what "agent-ready" means, the five things it takes, and why 2026 is the year it stops being optional. You run an app. Every week you open a dashboard, publish a few things, schedule a push, check yesterday's numbers, fix a price. That dashboard got friendlier every year — the whole no-code promise, and it worked. Millions of people now operate professional apps without code.But the operator is changing. People are starting to hand that weekly routine to an AI assistant: "Publish these three articles, schedule a push for each, and tell me which section lost readers last week." The assistant doesn't want a friendlier dashboard. It wants an interface it can call.That single fact reorders everything. The interface that wins the next decade isn't the one humans like best. It's the one an agent can drive.
Lesia PIETRI, Friday 12 June 2026

Build a Beautiful eCommerce App Faster with GoodBarber Themes

GoodBarber's theme library has always given merchants a professional head start, and it keeps growing. The latest additions are a set of eCommerce-oriented themes, each designed like a real brand with its own distinct look, proof of just how much range a GoodBarber app can have. Whatever style your store calls for, the right theme takes you from idea to launch far faster than designing everything yourself. If you run an online store or a local business, you already know how your brand should come across. The vision isn't the hard part. The hard part is translating it into a polished app, screen after screen, when design isn't your job. Which colors belong together? How big should the headings be? How do you keep everything consistent from one screen to the next? For most merchants, that's where the project quietly stalls: not in building the app, but in designing it.Starting from nothing sounds like creative freedom. More often it's a roadblock. What moves a project forward is a credible starting point: something that already looks right, ready to be shaped around your brand and your catalog instead of assembled piece by piece.
Pierre-Laurent Medori, Friday 12 June 2026

Use ChatGPT with GoodBarber: run your app without code

You've got a GoodBarber app. You've seen our announcements about the "MCP server," AI, "agent-ready" apps — and assumed all of it was for developers. It isn't. In five minutes, from ChatGPT, you can run your app just by talking to it: update a price, publish an article, send a push. No terminal, no code. Here's how, with five copy-paste prompts to get you started. Let's settle it right away, because it's the misunderstanding that stops everyone: you don't need any technical skills. No terminal, nothing to install, not a single command line. If you can write a message, you can run your app.The "MCP" our other articles talk about is simply the secure bridge between ChatGPT and your app. You'll never have to touch it, or even remember what those three letters stand for. You plug it in once, and you forget it.What you use is ChatGPT: the OpenAI assistant you've probably already opened a hundred times. The same chat window. The only difference, once it's connected to your app, is that it now knows how to act on it.We've been building tools for non-technical creators since 2011. This one follows the same rule as the rest: more power, less complexity.
Lesia PIETRI, Thursday 11 June 2026

A global floating button: one key action, visible everywhere in your app

The action you want from your users deserves to be reachable at all times, whether they are reading an article, browsing a product page, or moving from one tab to another. The Floating Button gives it exactly that place: a button defined once, present wherever your users need it, with no need to place it again screen by screen.
Pierre-Laurent Medori, Thursday 11 June 2026

How to automate your GoodBarber app with n8n and MCP — no code required

The short answer: with MCP, the API explains itself to the machine — you don't build requests by hand.A classic REST integration means reading API docs, building each HTTP request, handling auth and pagination yourself. MCP (Model Context Protocol) inverts that work: your GoodBarber app exposes its operations as tools that any MCP client can discover and call. Our test app — a Content App — exposed 62 tools the moment we connected: articles, paragraphs, events, maps, galleries, videos, sounds.n8n matters here because it's one of the rare automation platforms with a native MCP Client node — and because its AI Agent nodes can hand those 62 tools to Claude and let the model decide which to call. Zapier-style platforms automate apps; n8n + MCP automates your app.REST + classic automationMCP + n8nIntegration workOne hand-built request per actionTools discovered automaticallyAuthAPI keys per requestOne OAuth connectionAI in the loopYou parse, AI sees fragmentsThe agent calls tools directly
Pierre-Laurent Medori, Wednesday 10 June 2026

Your app is an AI backend: why agent-ready beats building AI agents

Every app platform in 2026 calls itself AI-powered. Bubble wants you to build AI agents. Lovable generates an app from a prompt. GoodBarber does something different — and, for most businesses, more useful: it turns the app you already run into an AI backend, a live system any AI agent can operate on your behalf. No-code app builders approach AI agent integration in two ways: they help you build agents, or they make your existing app callable by them.The agent-builder modelThe AI backend modelWhat the AI doesGenerates or powers your app's logicCalls your app's operations on your behalfYour starting pointBuild — or rebuild — on their platformYour existing app is already the targetWhere complexity livesIn workflows and databases you maintainIn the agent; your app simply respondsExamplesBubble, Lovable, Base44GoodBarber, through MCPBubble's pitch is sincere and, for its audience, accurate: if you're assembling a custom software product, building AI agents on Bubble's database-and-workflow engine is genuinely powerful. The same goes for prompt-to-app tools when what you need is a prototype by tonight.But notice what both ask of you first: a build. A schema, workflows, screens — or at the very least a migration.For a merchant with an existing app and real customers, that's the wrong starting point. You don't need to rebuild anything. You need your app to respond to AI commands.
Sergio Miranda Carvalho, Monday 8 June 2026

Age Protection: minor-safety compliance built into your native apps

Protecting underage users is no longer optional. A growing number of laws now require apps to adapt their behavior to a user's age — and getting it wrong can mean removal from the stores. Age Protection builds that compliance straight into your native GoodBarber apps, with no code on your side. Here's how to turn it on, and what changes for your users. Over the past few years, several countries — starting with the United States — have tightened the rules around protecting minors on digital platforms. These laws require apps to account for a user's age when deciding which features they can access. Any app that collects data, serves ads, or enables social interaction now has to apply specific restrictions whenever the user is a minor (under 16).On a custom-built app, that's real work: age detection, conditional logic on every sensitive feature, and ongoing maintenance every time the law changes. With GoodBarber, age verification is built natively into your iOS and Android apps. You flip one switch; the rest follows.