Apple's Guideline 4.2.6 keeps App Store submission with the client who provides the content

RuntimeWire lists what a builder can do on its own: generate source code, compile a build and help upload it to Apple's systems ^[13]. Apple's distribution documentation places TestFlight at the beta stage. Once testing is done, the developer sends the finished build to App Review, and the App Store release comes after that ^[7]. Guideline 4.2.6 applies at that final hand-off. The content provider is expected to submit, and the service is not ^[1].

By one employee's account, Newly stops before that step. Timurs Ragozins, an SEO intern at the AI app builder, told RuntimeWire that Newly ends at TestFlight because of 4.2.6 ^[14]. RuntimeWire notes that his claim of lost sales is his own report and was not independently verified ^[14]. Newly's public pages describe guided iOS publishing through Expo Launch, starting at $25 a month ^[5]. Founder and CEO Timothy Lindblom presents it as a compliance-aware service that generates React Native and Expo projects and lets users export the code ^[6]. The plainest public statement of where the product ends comes from its SEO intern ^[14].

FlutterFlow documents a split that fits the guideline's wording. The customer connects an App Store Connect API key and deploys a build from FlutterFlow. Then the customer finishes the listing and selects "Add for Review" in App Store Connect ^[8]. The builder holds a delegated credential for the upload. Submission stays a customer act.

Apple's text stops short of making that click the test. It does not say a customer must press a particular button, and it does not promise approval because the customer owns the developer account ^[4]. In a 2019 Apple Developer Forums exchange, a radio-app developer said rejections continued after clients used their own accounts and clicked submit themselves ^[15]. RuntimeWire treats that post as one developer's report, not a policy ruling ^[15]. In a 2026 thread about a branded app built from open-source software, an Apple staff developer said the final decision rested with App Review and pointed the developer to a review consultation ^[9]. RuntimeWire found no public rejection-rate data for 4.2.6 ^[10].

The other half of the guideline is about sameness. Apps made from a commercial template are the case 4.2.6 names ^[1]. Apple's two accepted routes are tools that let clients build customized apps with distinct user experiences, or one app that aggregates many clients' content ^[3]. Google's repetitive-content policy targets apps with highly similar functionality, content and user experience, and also suggests an aggregating app ^[11]. Google does not require the content provider to submit ^[11]. It does bar apps with limited functionality or content ^[12].

We think the FlutterFlow split is the right default for any builder selling into this market. Automate through upload on the customer's credential, and leave the listing and the submit in the customer's account. That keeps the service out of the submitting role the guideline reserves for the content provider ^[1]. It does nothing for the distinctness test, and App Review makes that call app by app ^[9].