Marc Leonardi, Thursday 20 August 2026

Mobile App Accessibility: How to Make Your App More Accessible

You cannot prove that an app is accessible from a preview or a contrast score. You can, however, remove a surprising number of barriers before formal testing begins.Mobile app accessibility extends well beyond color contrast. Typography, spacing, navigation, touch targets, labels, motion, media and assistive-technology behavior all affect whether someone can complete a task.WCAG is written for web content. The W3C's WCAG2Mobile guidance explains how WCAG 2.2 Level A and AA criteria can be applied to native, web and hybrid mobile apps. That document is informative rather than a separate normative mobile standard, and it is not sufficient on its own to establish that an app is accessible.This checklist separates what can be configured centrally from what still has to be verified in the published product:Accessibility areaFirst checkWhat to configure or testColor contrastText, backgrounds, controls and statesSet global colors and verify each contrast pairTypography and spacingReadable defaults, wrapping and enlargementConfigure the global type hierarchy and marginsNavigationClear destinations and labelsConfigure the app structure, labels and navigationTouch targetsControls are easy to operateVerify the generated app on devicesScreen readersNames, roles, states and focus orderTest the generated iOS and Android appsMotionEffects remain useful and optionalConfigure animations and haptics, then test system preferencesMediaCaptions, transcripts and text alternativesAdd alternatives during content creation and editorial reviewPWA interactionKeyboard, zoom, focus and responsive layoutsTest the published PWA in browsers
Marc Leonardi, Tuesday 18 August 2026

Mobile app privacy checklist: what to prepare before submission

Imagine a fitness coach app with member accounts, optional location, an email form and analytics. That is already four separate data paths. Change one feature and the privacy picture changes with it.The difficult part is not producing one legal page. It is making three surfaces describe the same app:SurfaceWhat it must reflectThe app itselfThe data, permissions and third-party services actually usedThe privacy policyWhat is collected, why, by whom, for how long and what users can do about itThe store declarationsApple App Privacy and Google Play Data safety answers based on the current appIf one surface says “no location data” while the submitted app requests location access, the problem is inconsistency.A large part of privacy preparation is a consistency exercise: the app, the policy and the store listing must tell the same story. Consistency is necessary, but it does not replace compliance with the stores’ underlying privacy and user-data rules.This article helps you prepare that story. It is not legal advice; applicable requirements vary by country, audience and type of data.
Pierre-Laurent Medori, Thursday 13 August 2026

Your app's MCP server now speaks the latest version of the protocol

Every GoodBarber app comes with its own MCP server. It is the secure doorway that lets an AI assistant, with your permission, read and manage your app: write and schedule articles, update products, check your stats, prepare push notifications. You connect the assistant once, it authenticates through OAuth, and it only ever sees your app.If you are discovering this, two good starting points: our MCP page explains how to connect an assistant to your app, and this article explains what makes an application MCP server different.
Pierre-Laurent Medori, Wednesday 12 August 2026

The production checklist AI-built apps fail (7 things that break after the demo)

The short version. An AI-built app that shines in a demo has proven it can render, not that it can run. Production is decided by seven boring things: accounts, empty states, store review, push delivery, the stack bill, the first update, and week-to-week operation. Run the seven checks below before you announce a launch date. On GoodBarber, the platform carries the first six, some pre-built, some as a service, and the seventh comes with an AI agent connection.You built an app with an AI app builder, or vibe-coded it prompt by prompt over a few evenings. It works. But look at the conditions under which it works: your phone, your Wi-Fi, your account, data you typed in yourself, a build generated an hour ago. A demo is an app tested exclusively under friendly conditions.Production ready means the opposite: the app keeps working once the friendly conditions are gone. Strangers instead of you, a reviewer instead of an audience, months instead of an afternoon.We have already written about why this gap exists: our article on the seven walls between a prototype and the stores maps the structural distance, and our piece on building an app versus running one names the work that starts after launch. Those articles end in questions worth asking yourself. This one turns the questions into experiments: seven checks, each with a concrete procedure and a pass condition you cannot argue with, all of them runnable this week. If a check feels boring, that is the point. Production is where the boring bugs live.
Lesia PIETRI, Friday 31 July 2026

New Classic Themes to Launch Your App Faster

The hardest part of a content app is rarely the content. It is making everything look intentional, screen after screen, when design is not your job. A theme solves that by handing you a complete visual direction: colors, typography, imagery style, and layout already working together. You bring your content and your brand; the theme brings the polish. And because every theme runs on Smart Design, the result stays consistent however far you customize it.
Dumè Siacci, Friday 31 July 2026

Will your app still work in three years?

What happens to an app in the three years after launch: what moves around it, what the platform absorbs on your behalf, and the short list of what stays in your name.
Muriel Santoni, Wednesday 29 July 2026

GoodBarber vs Replit

Replit has been building browser-based development tools since 2016. In early 2026 it added a mobile offer, under a page titled "Idea to Mobile App in Minutes" — which puts it, for the first time, on the same ground as an app builder.So we ran our standard brief through it — AURORA, the same luxury travel guide app we build on every tool in this series. Not a feature checklist: an actual app that has to reach the stores, get updated every week, and be operated by someone who does not write code.What comes out of Replit is real. It is also, unmistakably, a codebase — a React Native project, a metered cloud, and a development console. That is the whole comparison in one sentence: Replit answers you in plain language, then hands you something that behaves like an engineering project. Whether that is a gift or a problem depends entirely on who is going to run the app next Tuesday.
Florian Luccioni, Tuesday 28 July 2026

IndexNow on GoodBarber: get your PWA indexed faster

The SEO of a PWA rests on a simple principle: for a page to show up in search results, an engine first has to visit it, read it, and index it. That visit — the crawl — isn't something you trigger. The engine decides when it comes back, at its own pace.For a static site, that wait barely matters. For an app whose content is alive — a media outlet publishing several times a day, a store whose prices and stock keep shifting, a schedule where events appear and expire — it's a genuine drag. You've already done the work: the content is live, up to date, ready to be found. But it sits there waiting on a crawler that hasn't come back yet. In the meantime, it's sometimes an old version of the page — or nothing at all — that surfaces in results.
Mathieu Poli, Monday 27 July 2026

AI Extension Builder: custom article templates for your app

Name any content section of your app in your prompt, and the AI Extension Builder builds a section that displays that content — in the exact layout you described. Your articles, your template, always up to date. Every content section in a GoodBarber app comes with a set of carefully designed templates. You pick one, and it works — that's the point of an integrated platform. But the layout you have in mind isn't always in the list. Maybe you picture your latest articles magazine-style: one big cover photo with the title overlaid, smaller cards underneath. Or your events as a compact agenda with just the date and the venue. Until now, you picked the template that came closest.What many AI Extension Builder users haven't discovered is that this limit is gone. The builder doesn't just create standalone widgets — it can read the content of your app's existing sections. Which turns it into something more interesting than a widget generator: a tool for designing your own display templates.
Florian Luccioni, Thursday 23 July 2026

Read, cite, train: decide what AI does with your content

If you've published your PWA, it's serving a robots.txt right now — the first thing any crawler reads, and the file that decides what happens next: which parts of your site get fetched, and by whom. Yours has been saying yes to everyone.Everything below concerns that web version of your app. Your iOS and Android apps aren't crawled by anyone, and the tab only appears once your PWA has been published at least once — before that, there's no file to configure.That was a defensible answer. It just wasn't one you made — and the population it answers has changed. A few years ago, a crawler on your content was Google, Bing, or a scraper you didn't care about. Today a growing share of that traffic belongs to AI companies, and they don't all want the same thing from your pages. Treating them as one block means choosing between all of them and none of them.The new tab splits them into four families, in plain language: search engines (Google, Bing and the others that list your site in their results), AI answers (ChatGPT, Claude or Perplexity citing your site when they answer), AI training (robots collecting your content to train their models), and on-demand reading (someone asks an AI to open one specific page of your site). Four families, because those are four different deals.
Pierre-Laurent Medori, Thursday 23 July 2026

What quietly breaks when you don't update your app (and why you never notice on GoodBarber)

The short version. A mobile app that is not updated does not stay frozen: it decays. Push notifications quietly stop landing, new users stop finding it, and the stores eventually hide or remove it. On GoodBarber, the platform absorbs every OS and store change and ships the fix with your next update, so a year of mobile churn reaches you as a release note. The one thing you still have to do: update regularly.Your app works today. Leave it untouched for a year: it will still open, still look right, still do its job on your own phone. Nothing in your dashboard warns you. That is the trap.Because while your app stood still, everything underneath it moved. Apple and Google shipped new operating systems, rewrote store rules, retired old plumbing. You notice months later, through symptoms that look like a marketing problem: downloads sag, push campaigns reach fewer people, a loyal user writes that the app misbehaves on their new phone. The decay is real, and it has nothing to do with the quality of your content.
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.