“4.3”

For the last 2 years, our team at Panda has had one goal in mind: to change the failing connection application industry. The business model is severely flawed - evidenced in decline of users in match group etc (all public info). We are building the only connections app in the market without paid features – We Don't Play Games”. This in itself revolutionizes a space which currently commodifies human connection; true connections aren’t forged through super-likes, platinum memberships and such pay-to-win models, where users that don’t pay are unfairly disadvantaged. Key Differentiators: Never having paid features 50/50 Male-Female Ratio: Our app will ensure a balanced male-to-female ratio, something not found in other apps, especially in countries like India, where dating apps are dominated by men. This helps create a healthier, more equitable user experience for all genders. In a country like India, how can any connections app succeed with 99.9% men and 0.1% women? Panda Duos: A first-of-its-kind feature where

Hi everyone, I understand that Apple is cracking down on generic dating apps, and I totally agree that the App Store is full of low-effort clones. However, our app is a legitimate business with a real user base actively requesting an app version. Been operational since 2020 and serves users in Australia, the US, Canada, and Brazil, with over 57,000 monthly active users (MAUs). This isn’t a reskinned template or a quick-fix dating app—it’s an extension of a platform that users already trust and rely on. Our unique features include: Disappearing Photos & Voice Notes – Messages auto-delete after being viewed for better privacy. Private Galleries with Revocable Access – Users can share and revoke access to private albums anytime. We explained these points in our App Review Notes, but Apple keeps rejecting the app with the same template response about duplicate content in a saturated category. Has anyone successfully overcome this type of rejection for a dating app? Any advice would be greatly appreciated!

Hi Apple Developer community and Apple Review team, I'm hoping to get assistance with a persistent 4.3(a) rejection for our app ByGate (net.bygate.vpn). Submission ID: c8278a90-8e90-45b2-9256-d2e6b34e9518 Latest review date: May 19, 2026 Our situation: ByGate is not a generic VPN tool. It is a dedicated client application for ByGate's proprietary server infrastructure. The app works exclusively with ByGate servers - users cannot enter custom addresses, import third-party configurations, or connect to any other provider. It is functionally similar to a banking app or a streaming app: it only connects to one specific service. We have been operating ByGate as a cross-platform service: Android app live on Google Play Windows desktop app distributed via our website macOS desktop app distributed via our website Active paying subscriber base across all platforms Our existing users regularly contact our support team asking when the iOS version will be available. They are already using our servers and subscri

Hello, My app 岩片 (YanPian, Apple ID 6800534375, bundle ID com.ajin.heartrate) was rejected on September 19, 2026 under Guideline 4.3(a) - Design - Spam. Submission ID: 69a97b70-0219-42fe-861f-ce737bc19b38, version 1.0 (202609061946). The app is original. I wrote it myself, it is the only app on my account, I have not submitted similar apps on any other account, and I have never used or bought an app template. It is a tool for lead climbers who film their climbs from a tripod far below the wall: Heart-rate overlay: pick a climbing video from Photos. Heart-rate samples recorded by Apple Watch are read from HealthKit (read-only), matched to the video by capture time, and drawn on the video with a heart-rate graph. Zoom and follow: the climber is tiny in a wide shot, so the app crops in and follows them with editable keyframes (on-device person detection). Live capture, with an optional Zhiyun CQ5 gimbal that moves only when the climber is about to leave the frame, and an optional Apple Watch companion.

code write by flutter，and I never post by a other account，why？

We build and operate a management platform for fitness studios — bookings, memberships, payments, class schedules. We're planning the mobile side now and want to get the App Store model right before we build the release pipeline rather than after. What we have One codebase, which we write and maintain. It ships in two configurations from the same source: A marketplace app — every studio on the platform, searchable, with a picker. One binary, one listing, our brand. A per-studio configuration of that same app — identical functionality, with that studio's name, logo and colour palette, pointed at that studio's data. Studios ask for the second because they want their own presence in the store. Each one is a real business: real class schedules, real bookings, real payments taken by that studio, real members using it weekly. What I'm unsure about 4.2.6 Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. I ca