Apple Won’t Approve My App: How Should I Recast It for a New Direction?
If you’re building for the App Store, getting feedback from Apple’s review team can be a tough experience. After a year of development and multiple submission attempts, one developer shares a challenging journey: an app concept aimed at providing feedback on dating profiles, including prompts and messaging, was repeatedly rejected by Apple, who described it as “mean-spirited” and potentially hurtful to users. Even attempts to soften the tone, remove negative language, and emphasize positive reinforcement haven’t resolved the concerns.
What happened
– Core idea: A dating-profile review platform that offers feedback on an entire dating profile, including prompts and messaging. There was a paid tier for reviews from top-rated reviewers and a built-in chat component.
– Rejection pattern: Apple rejected the app multiple times, citing concerns about the potential to undermine users’ feelings.
– Attempts to adapt: The developer stripped features, revised wording to emphasize positivity, and tried to shift the concept to a more considerate, positive user experience, but approvals have not been granted.
– Current sentiment: The project remains in limbo after a year of effort, with a strong wish to deliver something that benefits people.
What to consider next
– Reframe the value proposition: Instead of a “review of dating profiles” that could be interpreted as judgmental, consider positioning the app around constructive feedback for self-improvement, confidence coaching, or profile optimization in a supportive environment.
– Emphasize well-being and safety: Align the app with positive, non-comparative feedback, consent-based participation, and resources for healthy dating experiences.
– Explore alternative use cases: The same technical foundation could be repurposed for different audiences and contexts, such as:
– Personal branding: Feedback on professional LinkedIn-like profiles or portfolios.
– Content optimization: Constructive critique for bios, prompts, or messaging on social platforms (without targeting dating dynamics).
– User experience testing: A platform for collecting user impressions on profile setups in a purely performance- or onboarding-focused context.
– Consider a different monetization and features model: If the “Superstar” reviewer concept was a concern, explore anonymized, opt-in feedback from a community of experts with strict guidelines, or substitute paid features with value-added analytics, not direct critiques of content others might find sensitive.
– Compliance and policy alignment: Review App Store guidelines relating to user-generated content, mental health considerations, and harassment policies. Build a compliance checklist early in the next iteration to avoid policy friction.
– Minimum viable product direction: Focus on a narrow, non-controversial scope that demonstrates safe, constructive feedback, with clear user protections and opt-in experiences.
Practical next steps
– Map a new value proposition: Draft 1–2 scenarios of how the app helps users improve messaging, profile clarity, or confidence in a positive, non-harmful way.
– Create a policy and guidelines doc: Outline how feedback is delivered, what is allowed, and how users can report concerns or opt out.
– Prototype a fresh concept: Build a minimal version focused on a single use case (e.g., profile optimization for professional or general social platforms) to iterate quickly.
– Seek external validation: Gather input from potential users in the new direction to ensure the concept resonates and aligns with platform policies.
– Prepare a re-submission plan: Once the concept is clarified and the features are aligned with policy, document the user flow, feedback model, and safety measures to present to the review team.
If you’d like, share more details about the new direction you’re considering (target audience, core value, and how feedback is delivered). I can help draft a revised product brief, feature backlog, and a policy-compliant messaging framework to improve your chances on the next iteration.
