Thanks for being a part of WWDC25!

How did we do? We’d love to know your thoughts on this year’s conference. Take the survey here

Struggling With Guideline 4.3(b) Rejections – Would Love Dev Insight

Hey everyone,

We recently submitted our new dating app, Rove Dating, and it’s been rejected under Guideline 4.3(b) — “Design: Spam.” I’d really appreciate your insights, especially from anyone who’s faced something similar or has experience getting nuanced apps approved in a saturated category.

Before building Rove, we spoke to dozens of users of existing dating platforms. We consistently heard the same thing: people are deeply dissatisfied with current apps. They’re overwhelmed, burned out by swiping, and frustrated by endless choices and low-quality interactions. It became clear that the problem isn’t that there are “too many” dating apps — it’s that most aren’t adapting to how people actually want to date in 2025.

We designed Rove to address those pain points head-on, with a totally different approach to matching, message limits, and emotional safety. We believe our app meaningfully improves the dating experience — but we’re having trouble getting that across in the review process.

Below is the explanation we’ve been submitting, which we feel strongly communicates how Rove is different. If anyone has tips, feedback, or even just a second set of eyes on how we’re presenting this, I’d be grateful!

––

Response to Guideline 4.3(b) – Design – Spam

We respectfully disagree with the assessment that Rove Dating duplicates existing apps. Rove is not a clone of existing dating apps — it introduces original interaction mechanics and novel safety features designed to address the growing frustration users feel toward current dating platforms.

What Makes Rove Dating Unique

Rove Dating is a highly curated experience that intentionally limits user engagement to foster more meaningful, emotionally safe interactions:

Key Differentiators:

•	No Swiping or Infinite Browsing: Users see a small, rotating selection instead of endless feeds.
•	Limited Conversations: Each user can have only 3 active conversations at a time.
•	“Shoot Your Shot” Mechanism:
•	Men can initiate contact with a limited set of women.
•	If a woman declines, the man can try with someone else — if not, he must wait.
•	Women can only receive inbound messages, helping prevent message fatigue.

This constraint-based system:

•	Reduces inbox overload (especially for women).
•	Encourages higher-quality, intentional messages.
•	Mimics real-life social dynamics — where opportunities are limited and meaningful.

Innovative Safety System: MPAA-Style Behavior Ratings

Rove also introduces a first-of-its-kind safety feature inspired by the MPAA film rating system:

•	Male users are assigned a community-informed behavioral safety rating (e.g., G, PG, R) based on in-app messaging analysis.
•	Women can quickly assess a match’s tone, trustworthiness, and vibe before engaging.
•	This system encourages respectful behavior and promotes a safer, more transparent dating environment.

This type of behavioral transparency does not exist in any other dating app currently on the App Store.

Conclusion

Rove is not another swipe-based clone. It is a thoughtfully reimagined dating platform built around scarcity, respect, and intentionality. Its mechanics — from conversation caps to safety scores — are fundamentally different from other offerings in the App Store’s dating category.

We hope you’ll reconsider Rove on the merits of its original features, purpose-driven design, and unique safety innovations.

Hello,

That's a thoughtful response.

You may need to provide more evidence of uniqueness to support this claim: "Its mechanics — from conversation caps to safety scores — are fundamentally different from other offerings in the App Store’s dating category."

Similarly, we recommend reaching out to App Review to provide more detailed feedback on how guideline 4.3(b) was applied.

Hey lifeofjer,

I'm really glad you shared this, because we’re going through a very similar situation right now with our app Cloose.

Although Cloose isn’t a dating app, Apple keeps interpreting it as one and rejecting us under 4.3(b) – Spam. Our concept is a social map, built around real-time location and spontaneous proximity, where users can connect if they happen to be nearby and active on the map — no swipe mechanics, no auto-matching, no profiles sorted like in dating apps. We even removed all “dating-like” terminology and visuals, including hearts, swipes, and the word “match.”

Still, we keep getting the same general response from Apple: that the app doesn’t provide a unique enough experience.

To really demonstrate how different our app is, we even created a full walkthrough video showing all the redesigned functionalities, safety mechanics, merge-based interaction logic, delayed/obfuscated location, and more. But honestly, we’re not sure if the review team has watched it.

Here’s the video, in case anyone is curious or in the same boat:

  • https://www.youtube.com/watch?v=ghpW62isR_Q

It’s clear you're trying to solve real user problems, and we are too — by rethinking how social proximity should work in mobile interactions, without replicating what the saturated dating space has done.

Thanks again for sharing, and best of luck with Rove. If I learn anything new about navigating this kind of rejection, I’ll come back and share.

— Carlos

Struggling With Guideline 4.3(b) Rejections – Would Love Dev Insight
 
 
Q