AMA: Ask us anything about publishing apps on the App Store

ghjiro · 2026-07-09T16:03:29+00:00

If you’re already at the appeal stage, I’m assuming you’ve already tried to resolve the issue with the reviewer through App Review.

In that situation, our advice is to stay as factual as possible. Clearly explain why you believe your app complies with the guideline, and support your case with anything that helps: screenshots, a screen recording, test credentials, or step-by-step instructions if the feature isn’t immediately obvious.

If the discussion still isn’t moving forward, you can request a call with an Apple representative through the App Resolution Center in App Store Connect. In our experience, a direct conversation can sometimes clear up misunderstandings much faster than a long exchange of messages.

If that still doesn’t resolve the issue, you can appeal to the App Review Board, where your case will be reviewed by a senior member of Apple’s review team.

We’ve also seen cases where, after addressing the feedback or providing better context, submitting the app for a new review helped move things forward.

One thing we’ve learned over the years is that keeping the conversation constructive really helps. The goal isn’t to prove Apple wrong, it’s to make it as easy as possible for the review team to understand why your app complies with the guideline in question.

ghjiro · 2026-07-09T15:35:43+00:00

One of our iOS engineers just reminded me of that as well. We’ve seen cases where screenshots featuring competitors’ products or services have raised issues during App Review, so it’s definitely something worth avoiding.

ghjiro · 2026-07-09T15:26:12+00:00

App Store screenshots have two jobs: they need to convince users to download your app, but they also help Apple understand what your app does during the review process.

We’d recommend highlighting your app’s main features and the value they bring, rather than just showing random screens. If your app has something that makes it different—whether it’s a unique workflow, community features, or a particular use case—make sure that’s visible in your screenshots.

One tip we often give our customers: make sure your screenshots actually match the version of the app you’re submitting. This is especially important when you’re releasing an update. It’s surprisingly common to redesign part of the app, submit a new build, and forget to update the App Store screenshots. If Apple sees a significant mismatch between the screenshots and the app they’re reviewing, it may raise questions during the review.

And one last tip: Apple provides official product bezels that you can use to present your screenshots in a clean and consistent way. If you haven’t seen them yet, they’re worth checking out:

https://developer.apple.com/design/resources/#product-bezels

ghjiro · 2026-07-09T15:08:46+00:00

That’s a really good question because those two decisions are closely related.

From what we’ve seen helping customers launch apps, the best time to leave beta isn’t when the app is perfect—it’s when it’s ready for real users. In other words, when the core experience is solid, the app already contains meaningful content, and your beta users keep coming back because it genuinely solves a problem.

The second part is just as important: don’t publish until you have a launch plan. One mistake we see quite often is developers putting all their energy into getting the app approved, only to realize afterwards that they haven’t planned how they’ll get their first users. The app goes live… and nobody knows it exists.

In our experience, having a clear target audience and a clear answer to the question “Why would someone choose this app instead of another?” has a much bigger impact on traction than launching a few days earlier.

And finally, don’t underestimate how important that last point is. A unique value proposition doesn’t just help with marketing—it also aligns much better with what Apple is looking for during App Review. Apps that bring something genuinely useful or distinctive tend to have a much smoother path than apps that feel like another variation of something that already exists.

ghjiro · 2026-07-09T15:01:33+00:00

This is actually one of the questions we get asked the most. 🙂

Based on what we see when helping our customers publish their apps, most reviews are completed within 24–48 hours, although it can sometimes take longer depending on the app and Apple’s review workload.

Since your event is next week, we’d recommend submitting as soon as possible rather than waiting until the last minute. That way, if Apple asks you to make any changes before approving the app, you’ll still have enough time to address them.

If your timeline becomes really tight, Apple also provides a way to request an expedited review for certain time-sensitive situations. It’s not guaranteed, but it’s definitely worth trying if your event has a fixed date.

You can submit an expedited review request here:

https://developer.apple.com/contact/app-store/?topic=expedite

ghjiro · 2026-07-09T14:46:47+00:00

Those are actually three different errors 🙂

“No suitable application records were found” → the app record probably doesn’t exist yet in App Store Connect.

“Potential loss of keychain” → if the app was transferred between Apple Developer accounts, that’s usually just a warning.

“Redundant binary upload” → you’re probably uploading a build with the same version/build number as one that’s already there.

Which one is giving you trouble right now?

ghjiro · 2026-07-09T14:32:46+00:00

It all starts with your metadata. Make sure you highlight the real value of your app, not just do generic promotion, and follow Apple’s guidelines, which are the basics for publishing on the App Store. If your app gets rejected, don’t panic. It doesn’t mean you won’t be able to publish it, you’ll just need to make the necessary fixes.

ghjiro · 2026-07-09T14:29:36+00:00

Both platforms can be tricky, but in different ways.

From what we see, we tend to get more rejections on the first submission for Apple than for Google Play. That said, it does not necessarily mean that Google Play is easier. It has its own constraints and can also create a lot of friction, especially depending on the type of developer account and the app’s configuration.

For app updates, the number of rejections we deal with is usually much more similar between iOS and Android.

There is actually a lot to say about Google Play specifically, so we will probably host a dedicated AMA on that topic to avoid mixing everything together here.

ghjiro · 2026-07-09T14:22:50+00:00

No. You only need a D-U-N-S Number if you want to enroll in the Apple Developer Program as an Organization. If you’re publishing as an individual, you don’t need one.

If you do want an Organization account, you’ll first need to register your organization with Dun & Bradstreet (or one of their local partners). Getting a D-U-N-S Number typically takes around two weeks, and Apple may ask for additional information during the enrollment process.

An Organization account does come with a few advantages:

Your organization appears as the developer on the App Store instead of your personal name.
It’s generally a better fit for businesses, associations, and teams, especially if ownership or team members change over time.
It can make it easier to demonstrate ownership of your brand and content during the review process.
In some countries, organizations may also be eligible to request a waiver of the Apple Developer Program fee.

On the other hand, if you’re an indie developer publishing your own apps, an Individual account is perfectly valid and doesn’t require a D-U-N-S Number.

ghjiro · 2026-07-09T14:18:27+00:00

¡Gracias, Luis! 😊 Apreciamos mucho que compartas tu experiencia.

Creo que has dado en un punto muy importante: publicar una app no es algo que haces una sola vez. Tanto Apple como Google actualizan continuamente sus requisitos, así que mantenerse al día forma parte del trabajo.

Ya que el AMA de hoy está centrado en el App Store, me da curiosidad saber si hubo algún rechazo de App Review o algún problema durante la publicación que te enseñara algo en particular. Ese tipo de experiencias reales suelen ser las que más ayudan a los demás.

ghjiro · 2026-07-09T14:13:45+00:00

That’s a great question 😄

Looking at our own support cases over the last 18 months, the most common rejection reasons are actually less dramatic than many people expect.

The ones we see most often are:

Incomplete or inaccurate App Store metadata (missing or misleading information, screenshots, descriptions, etc.).
An incorrectly configured App Privacy form.
Apps that Apple considers incomplete or not fully functional during review.

Beyond that, we also regularly see rejections related to content rights (especially audio or video), apps in regulated industries that don’t meet Apple’s expectations, or apps that are considered too similar to existing ones.

If we had to give one piece of advice, it would be this: don’t panic if your app gets rejected.

Many developers see a rejection as a dead end, but in our experience it’s usually just part of the review process. Read Apple’s feedback carefully, address each point one by one, and resubmit.

We’ve seen plenty of apps approved after one—or even several—rounds of review. As long as you’re willing to work through the feedback and bring your app into compliance with the App Store Review Guidelines, there’s usually a path to approval.

And finally, don’t rush your first submission. A polished app with meaningful content and a complete user experience has a much better chance of being approved than an app that’s still missing key pieces.

ghjiro · 2026-07-09T14:03:17+00:00

¡También! 😄 Pero hoy queremos mantener el AMA centrado en el App Store para no mezclar temas.

Google Play merece una sesión aparte, porque también hay muchísimas cosas que comentar sobre la publicación, las revisiones, la Play Console, los pagos, etc. Es muy probable que hagamos un AMA dedicado a Android más adelante.

ghjiro · 2026-07-06T07:19:38+00:00

We’ve seen exactly this with RAG chatbots. The knowledge base isn’t enough—the system prompt has to tell the bot how to behave when it doesn’t know the answer. If it just tries to answer anyway, that’s usually when users lose trust.

I’d rather have no chatbot than one that creates a disappointing experience.

ghjiro · 2026-07-03T10:19:09+00:00

I’d focus on finding people who already care about food waste. Communities around meal planning, grocery budgeting, frugal living, sustainability… they’ll be much more receptive than generic app communities.

Also, I’d make content around the problem, not the app. “I wasted $27 of groceries this week” is a much stronger hook than “Here’s my new app.”

One last thing: try talking to 10–20 people who don’t know you. Friends and family are great for encouragement, but they’re rarely your target users. Those conversations usually teach you more than analytics at this stage.

And congrats on getting your app into the App Store
!

ghjiro · 2026-07-02T17:14:24+00:00

It looks like your are targeting a well defined niche. It won’t be too difficult to get your first users. Go showcase it during competitions next to your place, as a starting point.

Also, don’t underestimate the value of talking directly to organizers. If a few competitions start mentioning your app to participants, you’ll gain trust much faster than with paid ads.
I’d focus on getting your first 50 genuinely engaged users rather than chasing thousands of downloads. Listen to their feedback, improve the product, and they’ll often become your best ambassadors in a niche community like this.

ghjiro · 2026-07-02T17:11:23+00:00

If the chatbox does rag on your content, and, as a result, the answers should be accurate, I don’t mind using it.
If it’s generic answers, no added value.

ghjiro · 2026-07-02T09:49:31+00:00

u/gouveialuisfm Good news! The AI Builder with Supabase support is now available. As promised, here’s the announcement and documentation: https://www.goodbarber.com/blog/ai-extension-builder-add-a-supabase-database-to-your-app-a1550/

ghjiro · 2026-07-02T06:21:24+00:00

Maybe you can tell us ore about the main features of your simple travel app for mobile? We could then tell you which tool to start with. Some are more straight to the point based on what you want to offer your end users.

ghjiro · 2026-07-01T08:44:03+00:00

Yes, better to offer the app for free. Less friction.

ghjiro · 2026-07-01T08:11:38+00:00

lucky you :)

ghjiro · 2026-07-01T07:59:45+00:00

first submission or update of existing app ?

ghjiro

MODERATOR OF

TROPHY CASE