Skip to main content
Question

How can developers flag integration intent early to avoid duplication rejections?

  • June 8, 2026
  • 1 reply
  • 507 views

Hello Community,

Is there any way to know if another developer is already working on a third-party integration before you start building?

We ask because we recently went through the full development cycle for an integration, only to find out during the review process that a similar app had been published while we were building. The marketplace duplication policy then resulted in a rejection.

It feels like there's a gap here for development teams who start in good faith when no integration exists, but then someone else publishes before them. Is there a formal way to flag your integration intent early, or an appeals process for cases like this?

Thank you in advance.

1 reply

  • New Participant
  • July 11, 2026

One thing that has helped me is communicating integration plans as early as possible. Creating an issue or proposal before starting development gives maintainers visibility, reduces duplicate work, and allows everyone to agree on the best implementation. I follow the same approach while maintaining projects like https://sportzfyapkapp.com, where planning features early helps avoid unnecessary redesigns and saves development time.