Hi everyone,
I am seeking advice from developers who have successfully resolved or navigated Guideline 4.3(b) (Design: Spam / Saturated Category) rejections, especially within the dating or social networking space.
App Overview & Core Features: Our app is a "Diary-based Dating / Emotional Connection Platform." Unlike traditional photo-first, swipe-deck dating apps, our core mechanics rely on authentic emotional reflection:
Journal/Diary-First Discovery: Users write daily diary entries reflecting their thoughts and emotions. Matching and interaction occur based on mutual empathy with these journal entries.
Identity Verification: All users are identity-verified to maintain authenticity and safety.
24/7 AI Moderation: We run continuous AI verification on profile content, posts, and real-time chat to prevent spam, abuse, and inappropriate content.
Text-to-Profile UX: Users read daily self-written introductions first, and profiles only unlock after reading the text.
Current Situation:
We received a 4.3(b) rejection stating that the app primarily includes dating features duplicating existing apps on the App Store.
We appealed to the App Review Board (APL527511) and explained our rebuilt UX (removing photo grids, prioritizing text/diary entries), but received a template rejection stating the category is saturated.
We have requested an App Review Appointment and are waiting for guidance.
Questions for the Community:
Has anyone successfully overcome 4.3(b) for a dating/social app by reframing metadata, category placement (e.g., Lifestyle/Mental Wellbeing instead of Social Networking), or onboarding flows?
Is a 4.3(b) flag tied permanently to a Bundle ID once flagged multiple times, or is it possible to pass review after adjusting the core positioning?
How did you effectively demonstrate to the review team during an App Review Call that your app provides a non-traditional, unique user experience?
Any insights, experiences, or advice would be greatly appreciated.
Thank you!