My dating app has now been rejected by Apple under Guideline 4.3(b) for the fourth time.
The reason given is that the App Store already contains enough apps in this category.
I understand that Apple does not want duplicate or copycat apps. However, my app is not simply another dating app with a different name and design.
The app has several core features specifically built around real-life dating:
-
Real Date Score: Users receive a score based on completed real-life dates. This score is displayed on their profile and helps other users understand whether someone actually goes on dates and follows through.
-
Real Date Planner: Users can plan real-life dates through the app.
-
Group Dates: Users can organize dates with groups of up to 10 people.
-
Group Chat: Up to 10 people can participate in a group conversation.
-
Ghosting Protection: Users who repeatedly ghost after matching can be permanently banned.
-
Mandatory Selfie Verification: Users must complete verification to use the platform.
-
Singles & Couples: The app supports both individual and couple profiles.
I have searched the App Store for an app that provides the same concept, particularly a dating profile that publicly displays a score based on completed real-life dates.
I have not found one.
If Apple considers this app substantially equivalent to existing apps under Guideline 4.3(b), I would like to know:
Which existing App Store app provides these same core functionalities, particularly the Real Date Score and the system that permanently bans users for repeated ghosting?
I am not claiming that no other dating app has any individual feature that overlaps with mine. Of course there are common dating-app features.
The question is whether the overall product concept and core functionality are sufficiently different from existing apps to justify its presence on the App Store.
This is not only unfair but also an anti-competitive approach. It is certainly not something befitting a giant like Apple.
This is now the fourth 4.3(b) rejection, so I would appreciate clarification from developers who have encountered the same situation or from anyone familiar with how Apple evaluates this type of differentiation.