Product Thumbnail

Rubber Duck

Catch App Store rejection issues before Apple does.

Analytics
Developer Tools
Apple

Rubber Duck scans your iOS app before you submit it to the App Store. We combine automated checks with human testers on real devices to catch the issues Apple flags the most: crashes, incomplete build flows, missing privacy data, inconsistent metadata, broken onboarding, and more. Upload your IPA → we test → you get a clear actionable Duck Report.

Top comment

Hi everyone! I'm the maker of Rubber Duck. After shipping iOS apps, I realized how unpredictable App Store review can be. Even great apps get rejected for:

  • Missing metadata

  • Small UI issues

  • Broken flows on certain iPhone models

  • Forgotten privacy entries

  • One-off crashes Apple found

Each rejection set the launch back days. So I built Rubber Duck to be the “review before the review.” It combines automated checks with human testers using real iPhones like an App Store reviewer, but faster and kinder.

Excited to hear what you think and how we can make this even more useful!

Comment highlights

Congrats on the launch! The hybrid approach of automation + human testers is super smart. How fast is the typical turnaround time for a full Duck Report after uploading an IPA?

This is clever — catching App Store rejections before submission saves so much time.

What are the most common rejection reasons it catches?

Also, does it check for the vague "Guideline 4.3" spam filter stuff?

Nice work 👏

@Rubber Duck This is super practical! App Store rejection is brutal, especially when you've already invested weeks into a build.

Does Rubber Duck catch design guideline issues (like non-standard UI patterns), or is it mainly technical/metadata focused?

Also curious if it flags accessibility problems before Apple does—that's becoming a bigger rejection reason lately.

So you still need humans at background this is not fully automated right ?

Wow, Rubber Duck sounds super helpful! 😄 Scanning your iOS app before App Store submission and combining automated checks with real-device testing is such a smart approach. Love the clear Duck Report idea it must save so much time and stress!

I could see how our tool could pair nicely with Rubberduck to streamline user insights and feedback loops, and I’m feeling inspired to take a closer look at their launch and explore the integration possibilities myself.

Will use this for my first iOS app launch. I’m a huge fan of getting in front of problems before they occur. Love it! 

Oof, this would’ve saved me a week last spring. Got dinged for a missing privacy string and a weird crash only on iPhone SE. Like the human-on-real-device bit. How deep do your automated checks go? e.g., Info.plist sanity + broken onboarding paths?

Hey @sayuj_suresh, I'm the founder of Vicaura, also launched today on product hunt. Just checked out Rubber Duck. Very useful. Appstore rejections are a major pain. Congrats on the launch. Would love to connect and chat sometime.

Very useful tool 👍🏻 How do you match your tests with App Store validations?

Huge congrats on shipping! I can already see this becoming essential for small teams launching apps.

Hey Sayuj, this resonates! I’m curious what was the rejection that finally made you snap and say okay, I’m building something to fix this? Like, was there one that felt especially painful or ridiculous that pushed you over the edge?

@sayuj_suresh This is such a smart gap to solve, so many teams only discover App Store issues after a rejected submission. Having a pre-submission “duck check” that blends automated scans with real human testers feels like the kind of tool every iOS dev wishes existed sooner.

How deep do your automated checks go? Are you able to flag things like missing privacy manifests or issues with entitlement usage before Apple does?

I like it as it's always frustrating that after submitting an app for review you sometimes have to wait 1 week, before then getting back a "Rejected" just because you forgot to add a single visible button like the Restore Purchase button. So 1 week wasted for nothing. Will your solution also check for things like what I just mentioned? Because then it will be fire and something I will use for my next releases!