App Store Review

Archeden ART

Resubmission packet

Everything needed to answer the rejection under Guidelines 4.3 and 4.2.6: whether a new build is required, what the app has to change first, every paid flow a reviewer can reach on iOS, and the nine answers written to match the build you upload.

Verdict

A new build is required before you resubmit

The nine written answers cannot clear this rejection on their own. Apple allows a same-build resubmission when the problem is only the wording of metadata, but the payment statement on file does not match what a reviewer can reach inside the iOS app. That is treated as a problem with the app, so the build has to change first and the answers have to describe the build you upload.

  • The earlier Guideline 3.1.1 reply told Apple the iOS app is free and has no purchase path while the build under review did behave that way in part. That reply is now marked void so it cannot be sent by mistake.
  • Digital selling has to be absent from iOS rather than worded around: no price, no purchase button and no link out for a subscription, a one-time purchase of a creator’s work, or a tip.
  • The build you upload has to be the build your review notes describe: the same sign-in, the same age gate, the same screens in the recording.

What is only metadata

  • The nine answers themselves are metadata and can be edited in App Store Connect.
  • The age rating, the app description and the review notes are metadata too, and each has to agree with the new build.

Payment approach

In-app purchase cannot be built in this app as it stands

Apple in-app purchase is the right model for digital sales under Guideline 3.1.1, and it is not implementable on the current architecture. Archeden ART is a packaged web app running on Base44. That runtime has no StoreKit, so there is no product catalogue, no purchase sheet, no transaction result to read, and no receipt to trust.

  • StoreKit itself: a purchase cannot be started, so there is nothing for a reviewer to buy.
  • Signed-transaction or receipt verification, so an entitlement could never be trusted even if a purchase were made.
  • App Store Server Notifications, so a refund, cancellation or billing failure could not switch access off.
  • A restore path, which Apple requires for any non-consumable or subscription.

What exists today and must not be presented as IAP: One function accepts a transaction identifier from the client and switches an account on. It does not verify anything with Apple, so any signed-in caller can send a well-formed number and become entitled. It is a placeholder, not an in-app purchase implementation, and it is not wired to a StoreKit purchase anywhere in the app.

The three routes

01

Ship iOS without digital selling

What this build does now that every digital path is closed. No subscription, purchase or tip is offered on iOS, and access to digital content is free there. Fastest route back to review, and it is the only one available without leaving this platform. The cost is no digital revenue from iOS users.

02

Build a native iOS app with StoreKit, outside this platform

A real in-app purchase implementation: products in App Store Connect, purchase and restore flows, server-side signed-transaction verification, and App Store Server Notifications updating entitlements. It keeps this web app as the backend, but it is a second app to build and maintain, and it cannot reuse the packaged build.

03

Hold the submission

Answer Apple without resubmitting until either route above is finished, so the reply and the build agree whenever the next review starts.

The earlier reply is still on file and still wrong

The Guideline 3.1.1 reply kept in this app’s public files states that the iOS build has no checkout, no tipping and no purchase path at all. That was not true of the build under review, and a reply that contradicts the binary is how a wording problem becomes a second rejection.

Delete that file, or mark it void, before opening App Store Connect. Nothing in this packet repeats its claims, and none of the nine answers assert that the payment model already complies with 3.1.1.

If the recording still shows a checkout sheet for digital content, it demonstrates the problem rather than resolving it. Re-cut it on the new build.

Payment surface audit

Every paid flow, and what iOS does with it

Apple’s rule applies to digital content unlocked inside the app. Tickets to a real concert, merchandise that ships, and a booking for a venue are ordinary commerce and may stay. Anything digital must not be sold on iOS in this build.

Membership subscription

Paywall, subscription gate · Digital

Closed on iOS

On iOS the gate grants access and renders no plan, no price and no button.

One-time purchase of a creator’s work

Buy dialog on a media item · Digital

Closed on iOS

The dialog returns nothing on iOS, so neither price nor button reaches the screen.

Tips to a creator

Tip dialog · Digital

Closed on iOS

Returns nothing on iOS, and the card form never mounts.

Subscription management

Subscription management screen · Digital

Closed on iOS

The billing portal is closed on iOS, so a subscription cannot be started or changed there.

Paid mashup commission

Mashup dashboard · Digital

Closed in this pass

A paid commission of digital work started a web checkout inside the iOS app. Closed in this pass.

Ad campaign purchase

Advertiser payment step · Digital

Closed in this pass

Promoting your own content inside the app is a digital service and ran a web checkout on iOS. Closed in this pass.

Web tip landing page

Web tip page · Digital

Closed in this pass

A web_checkout=1 parameter used to turn the iOS gate off, so a link carrying it rendered a card form on a phone. The parameter no longer affects the gate, and the tip page shows a plain notice on iOS. Closed in this pass.

Event and concert tickets

Event details, concert info · Real world

Closed on iOS

Admission to a real-world event, paid outside Apple’s rules for digital content. Say so in the notes so the reviewer expects a checkout.

Merchandise

Event details · Real world

Closed on iOS

Physical goods shipped to a buyer, paid by card as ordinary commerce.

Venue and performance bookings

Venue inquiry, booking payment · Real world

Closed on iOS

A service performed at a venue away from the app, not content unlocked inside it.

In the build

These change the app, so they need a new package uploaded before resubmitting.

  • Close the paid mashup commission on iOSDone

    Digital work commissioned in the app no longer starts a checkout on iOS.

  • Close the ad campaign purchase on iOSDone

    Promotion of content inside the app no longer starts a checkout on iOS.

  • Stop the web tip parameter disabling the iOS gateDone

    The gate now depends on the device only, so no link can switch it off inside the iOS app, and the tip page shows a notice there instead of a card form.

  • Walk the reviewer path on a deviceOpen

    Sign in, pass the age gate, open the globe, open a portfolio, follow, report a piece, block a user, then delete the account. Fix anything that dead-ends.

  • Cut the screen recording on the build you uploadOpen

    On a physical device, showing the globe walkthrough and no checkout sheet for digital content.

  • Rebuild the iOS package and upload itOpen

    The uploaded build has to contain the changes above, or the answers describe a different app.

In App Store Connect

These are edited in the submission itself and travel with the build above.

  • Replace answer 1 with the platform-specific wordingDone

    It now states what the iOS build does and does not sell, instead of claiming paid features are present in every build.

  • Void the old Guideline 3.1.1 replyDone

    Marked void in the public files, so it can no longer be sent by mistake. Delete it outright if you prefer.

  • Make the age rating agree with the buildOpen

    The rating, the audience description in answer 2 and the gating in the build must say the same thing.

  • Fill in the demo account and its lifetimeOpen

    A working sign-in that stays active through review, in the App Review notes.

  • Replace the example device list with the real oneOpen

    Only the devices and OS versions the build was actually opened on.

  • Describe the testing honestly in the notesOpen

    The same informal testing as answer 4, not a TestFlight programme.

Decisions only you can make

  • Which route for digital revenue: ship iOS without selling, or build a native StoreKit app outside this platform.
  • Whether tips should be offered on iOS at all when that revenue returns.
  • The age rating, and whether the build’s gating matches it.
  • The names and scope of the other apps on this developer account. You confirmed the account publishes them; answers 5, 6 and 7 each need one sentence per app.

What is left, and who does it

Three groups. The first is already in the app. The other two cannot be closed by changing code, so treat them as your own to-do list before you answer Apple.

Done in the app

Checked against this codebase. No action needed from you.

  • No digital purchase path on iOS:

    Membership, one-time purchases, tips, the billing portal, paid mashups and ad campaigns render no price, no button and no link on iOS.

  • A URL cannot reopen the iOS gate:

    The gate reads the device only, so no link or parameter can bring a checkout back on a phone.

  • Mature content filtered where the data is read:

    Age gating runs inside the media query on the public discovery, portfolio and following surfaces, so a flagged item cannot arrive beyond the first page.

  • Age assurance at first sign-in:

    Date of birth is collected once. Under 13 loses the social features; under 17 loses mature content.

  • Reporting, blocking and account deletion:

    Each exists and is reachable, so moderation is not a dead end for a reviewer.

  • Real-world iOS payments kept:

    Tickets, merchandise and venue or performance bookings still check out on iOS, as ordinary commerce.

Only you can answer these

Facts about your account and your testing. None of them can be read from the code.

  • Names and scope of the other apps on your account:

    One sentence per app for answers 5 and 6, plus whether any first-party code or asset is shared with them for answer 7.

  • Two or three real beta observations:

    The comment a tester made and the change it produced in the build you upload, for answer 4 and notes section 2b.

  • The demo account:

    An email and password that work, with content already loaded, kept active for the whole review.

  • The devices and OS versions you actually tested on:

    The example list in the notes is not a record and has to be replaced or deleted.

In App Store Connect and on a device

None of this happens by editing the app.

  • Rebuild and upload the iOS package:

    The uploaded build has to contain the closed payment paths above, or the answers describe a different app.

  • Set the age rating and make it agree:

    The rating, the audience description in answer 2 and the gating in the build must say the same thing.

  • App Privacy answers and the privacy policy URL:

    Tracking is No, and the policy URL goes in the app metadata.

  • Record the screen recording on that build:

    On a physical device, walking the reviewer path, with no checkout sheet for digital content in it.

  • Send the nine answers and the review notes:

    Only once the amber blocks are replaced and the statements match the build that is waiting for review.

The nine answers

Answer these in App Store Connect

Text in amber is a fact only you can confirm. Amber notes under an answer are evidence gaps for you, never part of the copied text. Copy an answer once its amber blocks have been replaced.

01

Describe in detail what this app does and the primary problem it solves for users.

Archeden ART is a discovery, publishing and monetization platform for independent artists, and for the audiences who want to find them. Its defining experience is discovery by place. A visitor opens the app onto an interactive 3D globe, turns it, selects a country, then a state or county, and sees the artists and the work anchored there: a painter in a small town, a band that plays one region, an illustrator whose portfolio sits where they live. Tapping through opens that artist's profile and portfolio (images, video, audio and 3D work) and the ways to follow or support them. The globe is the home screen, not a feature buried in a menu, and the same place filters carry through the gallery, playlists, events near the listener, and booking. From that starting point the app carries the rest of what an independent artist needs: a portfolio with upload and hosting for video, audio, images and 3D models; a listening and library layer (playlists, liked work, following, radio); a social layer (friends, messages, group chats); live performance tools (event listings, ticketing, and venue-to-performer booking with direct negotiation); and creation studios for drawing, pixel art, 3D modelling, music, ebooks, audiobooks, video and simple games, so work can be made where it is published. Commerce is split by platform, and this answer describes the build a reviewer opens on iOS. The iOS app does not sell or unlock digital content: a subscription, a one-time purchase of a creator's work and tips are not offered there, no price is shown for them, and no button or link leads to a purchase. The web app at our own site carries those transactions for the audience that uses it there. The only paid flows reachable on iOS are event and concert tickets, merchandise that ships to a buyer, and venue or performance bookings, which are real-world goods and services rather than digital content unlocked inside the app. The primary problem is twofold. First, fragmentation: an independent artist needs a media host, a storefront, a payment account, a booking system and several social networks to reach anyone, and none of them connects to the others. Second, reach: on a global feed, discovery is a function of a ranking, so an artist's audience and their region are irrelevant to whether they are seen. Archeden ART replaces the ranking with a place. An audience can ask what is being made somewhere and get a real answer, and an artist outside a cultural centre holds a durable, findable position rather than a temporary moment in a feed. On Guidelines 4.3 and 4.2.6 specifically: this is not a template, a white-label build of an existing product, or a wrapper around another service's catalogue. The concept, information architecture, navigation model, data model and feature set were defined by us as the app's owner and built for this app alone. The studios inside it produce media at the user's direction (a drawing, a track, a 3D scene, a document); they do not generate applications, and no user can use them to produce an app, a storefront, or a copy of this product.
02

Who is the intended user of this app? Provide a detailed description of the specific target audience.

Two primary groups, plus two secondary ones. Independent creators: solo musicians and songwriters, spoken-word and poetry artists, authors and audiobook creators, illustrators, photographers, 3D and game-asset creators, filmmakers, and performing artists such as bands, DJs and comedians. Typically self-managing, without label, publisher or agency backing, active on social platforms but frustrated that reach depends on a ranking rather than on the audience they have built. Often based outside major cultural centres, and looking for listeners beyond their own region. They use the app to make work, publish it, build a following, and be paid directly by that following. Culture-seeking audiences: people who are curious about what is being made where. Music listeners who want to discover by place and genre, readers and audiobook listeners, people interested in visual art and 3D work, and people who want to find live performance near them. They browse, listen, read, follow, and in some cases buy or subscribe. Secondary users are venues, event organisers and promoters, who use the booking and ticketing tools to find and engage performers, and people drawn to the app's public-domain and heritage collections, which sit alongside living artists rather than in a separate institutional archive. [Confirm the app's age rating before submitting. The App Review notes describe a 13+ rating. The rating, this audience description and the age gating in the build must say the same thing.]
03

What need or gap in the market does this app address that existing apps do not currently address, or address less effectively? Provide a detailed, substantive explanation.

Each need Archeden ART meets is served today by a product that does one slice of it. Streaming services distribute recorded music but give an independent artist no portfolio, no booking and no direct relationship with a listener. Social platforms optimise a global feed, so reach is a function of virality, and nothing about where an artist is from survives the experience. Marketplaces for 3D models, stock imagery and audio sell files but are disconnected from the tools used to make them, so a creator makes work in one app and sells it in another. Booking products are built for agencies and venue CRM teams, not for a solo performer taking a first booking. Archives for public-domain art and literature are separate destinations, unconnected to the artists working in the same tradition now. What is missing is a product that treats those as one continuous path (make, publish, be found, be paid) and that organises discovery around place rather than around an engagement ranking. Archeden ART does both, and the two decisions depend on each other: geography is the navigation model, so the same record of where an artist is based powers discovery on the globe, filtering, events near a listener, and booking between a venue and a performer. That produces a discovery question no feed-based product can answer, and it gives an artist a reason to be listed that does not expire when a post stops being amplified. Because the studios, the portfolio, the audience and the booking tools are one system, an artist's work, followers, sales and enquiries live in one place instead of across five subscriptions. The evidence that the concept is built and working is the app itself. A reviewer can see it in four steps. First, launch: the app opens on the interactive globe rather than a feed. Second, drill down: select a country, then a state or county, and the artists and work anchored there are listed. Third, open a portfolio: select an artist from that list and their work opens with the follow and support actions. Fourth, publish: from the workspace menu, upload a piece of work and it appears in the portfolio it belongs to.
04

What beta testing did you conduct before submitting the app for review? Provide examples of user feedback provided in beta that was applied to the production build.

Testing before submission was informal rather than a managed beta programme, and we are describing it accurately rather than presenting it as something larger. The app was put in front of a small number of people drawn from the artists and listeners already in contact with us. They used it as ordinary participants on their own devices, without a test script, a recruited cohort, or a distribution programme such as TestFlight, and there is no session log or written record of individual observations. Feedback arrived in conversation and in messages while they used the app, and it was applied during development rather than collected after a fixed test period. That feedback was not recorded in a form that ties a specific observation to a specific change with a date, so we are not presenting reconstructed before-and-after examples as if they were documented. The areas the testing was concentrated on are the ones most likely to break in a real user's hands: creating a profile and publishing a first piece of work, finding something through the globe, and reaching a paid flow. The same testing covered the areas that matter most for review and for user safety: age assurance at first sign-in, gating of mature content, reporting and blocking, and account deletion. [Insert two or three real examples here before submitting, one sentence each: the observation a tester made, and the change it produced in the build you upload. You have said you can provide these. Apple asked for them and this answer is incomplete without them.]

Evidence gap, not for submission

Apple asked for before-and-after examples and none are in this file yet. You confirmed you can supply them: add them above, then send the answer. Do not reconstruct examples you cannot point at directly, because the notes section 2b has to carry the same ones.

05

Is this app intended to function as a standalone product, or is it part of a suite of related apps published under your developer account? If part of a suite, provide a detailed description of how this app’s scope and functionality differ from each other app in the suite.

Archeden ART is submitted as a standalone product. It is not a companion viewer for another product, a demonstration build, or a feature of an app distributed separately: it carries its own concept, its own data model, its own account system, its own creation and publishing tools, its own commerce and booking features, and its own handling of user-generated content. [This developer account publishes other apps. Before submitting, add one sentence per app describing how its scope and functionality differ from Archeden ART. Name each app as it appears in App Store Connect. This answer is incomplete until those sentences are here.]
06

Could the functionality of this app be fully delivered as an in-app purchase, feature expansion, or content addition within any other app on your developer account? If so, provide a detailed explanation of why this functionality was not consolidated into that existing app.

No. The app is not a content pack or a single capability. It is a complete environment with its own account system, media pipeline, creation studios, marketplace, booking and ticketing system, social graph, and moderation process. Delivering it as an addition inside another app would mean embedding that entire surface in a product built for a different purpose: the host app's stated purpose would no longer describe what it does, a large volume of unrelated user-generated content and payments would be added to its review and safety obligations, and the result would be a listing whose primary function is not the one it advertises. It would also put two unrelated audiences under one listing and one set of commerce rules. [The account holds other apps. Before submitting, state here why this functionality was not consolidated into each of them, one sentence per app, consistent with the app list you give in answer 5.]
07

Does this app’s binary share any significant code, frameworks, or assets with any other app on your developer account, beyond standard third-party frameworks? If so, identify each shared component and describe its role in detail.

This developer account publishes other apps, and each was built as its own product rather than as a variant of Archeden ART. No first-party code or asset from Archeden ART is reused by another app on the account. What the apps have in common is the platform they run on and the standard open-source frameworks listed below. Archeden ART is built and hosted on Base44, a managed application platform. Base44 supplies the runtime and the backend services the app depends on: hosting, authentication, the database, file storage, email delivery and server-side functions. We used Base44 as the environment in which the application was built, and we operate the app on it. We do not have separate native code, a separate backend, or a separate asset pipeline that is also used elsewhere. What is specific to Archeden ART, and was defined by us as the app's owner, is the product itself: the concept of discovery by place, the information architecture, the globe as the primary navigation surface, the feature set from studios through portfolio and booking, the data model that supports all of it, and the name, brand and design. The third-party components are standard and serve these roles: React and React Router (interface and navigation), Tailwind CSS (styling), Three.js (3D rendering for the globe and the modelling studios), Recharts (charts in creator analytics), Leaflet with OpenStreetMap tiles (maps for shows, venues and tour routing), Framer Motion (animation), and Stripe (payments). Base44 is the platform described above. These are general-purpose frameworks and platform services, in the way two unrelated apps might both build on UIKit and a common cloud database. [Required before submitting: one line per other app on this account confirming that it was built separately and that the only shared elements are the common platform and open-source frameworks. If any first-party code, framework or asset really is shared, name it here and describe its role in both apps instead of claiming there is none.]
08

Does this app share any codebase, SDK, or content library with any third-party app, beyond standard third-party frameworks? If so, identify the shared component and provide a detailed explanation of the original functionality this app adds beyond it.

Only through standard third-party frameworks, platform services, public-domain works, and content our own users upload. No third-party app's proprietary codebase, SDK or content library is used. Software and services, with their role: Base44: managed application platform providing hosting, authentication, database, file storage, email delivery and server-side functions. Stripe: payment processing, subscription billing and payouts to creators in the web app; no digital sale in the iOS build runs through it. Three.js: 3D rendering for the globe and the 3D studios. Leaflet with OpenStreetMap tiles: map rendering for shows, venues and tour routing. Recharts: data visualisation in creator analytics. React, React Router, Tailwind CSS and Framer Motion: interface construction and animation. Optional connected services that a user authorises themselves, such as Google Calendar for calendar sync and Instagram for publishing, used only on that user's own authorisation to move their own content. On content, there are three distinct sources, and it is worth being precise about them. Creator content is uploaded by our users, who keep their rights in it and publish it under our terms. Public-domain works (visual art, literature, film and music) come from open public-domain collections, including museum open-access data, and are shown with attribution. Platform media is limited to our own brand assets and imagery. No other app's catalogue is bundled or served. Regarding Guideline 4.2.6, no part of the app generates applications. There is no app builder, no template marketplace that emits apps, and no path by which a user can produce an app, a storefront or a clone of this product from inside it. The studios generate media at the user's direction, which is ordinary creative tooling, and every output stays inside this app as that user's work. What Archeden ART adds beyond all of the above is the product: the geographic discovery model built on the globe, the integrated studios, the portfolio and publishing system, the artist commerce and booking stack, and the community and moderation features that support them. None of the components listed above provides any of that. They are implementation detail for a product that did not exist before we built it.
09

Was this app created for a client, partner, or other third party who provided the app’s content, concept, or branding? If so, identify who provided the content and provide a detailed explanation of why the app is submitted under your developer account rather than theirs.

No. Archeden ART was conceived, designed and built as our own independent project, and it is owned and operated by us. The concept of discovery by place, the product design and information architecture, the feature set, and the branding, including the Archeden ART name and the "A World of Worlds" tagline, were created by us as the app's owner. No client, partner or other third party commissioned the app, supplied its concept or branding, directs its content, or holds an ownership interest in it. Two things should not be confused with third-party authorship. First, the platform: we built and run the app on Base44, which supplies hosting, authentication, the database, storage, email and server-side functions, as described in answers 7 and 8. That is a service relationship, not a client or partner relationship, and it does not carry any ownership of the app. Second, content: our users upload and own the work they publish, and the app includes public-domain works used under their public-domain status with attribution. Neither makes the app someone else's product. The app is submitted under this developer account because the account belongs to the app's owner, the same person who conceived, funded and built it, and who operates it and answers for its content.

Reviewer walkthrough

What to put in the App Review notes

Only send these steps once each one has been walked on the build you upload. If a step dead-ends, fix it or drop the step, because a note the app contradicts is worse than no note.

  1. 01

    Sign in with the demo account

    Expected: The globe loads as the home screen. No subscription prompt appears.

  2. 02

    Complete the age gate if it appears

    Expected: Date of birth is requested once at first sign-in. Under 13 loses the social features; under 17 loses mature content.

  3. 03

    Select a country, then a state or county on the globe

    Expected: Artists and work anchored to that place are listed, not a global feed.

  4. 04

    Open an artist from that list

    Expected: Portfolio opens with follow and report actions. On iOS there is no price and no purchase button on digital work.

  5. 05

    Publish a piece of your own from the workspace menu

    Expected: The upload completes and the work appears in your portfolio.

  6. 06

    Report a piece of content, then block a user

    Expected: Both complete and are findable again, so moderation is not a dead end.

  7. 07

    Delete the account from the account settings

    Expected: Deletion runs and the session ends.

  8. 08

    Check the only paid flows left on iOS

    Expected: Event and concert tickets, merchandise, and venue or performance bookings. These are real-world goods and services, not digital content.

Never say this

Each of these would misdescribe the app, and a reply that contradicts the build is how a wording problem becomes a second rejection.

  • That in-app purchase, StoreKit or Apple transaction verification works in this app. It does not exist in this build.
  • That purchases restore through Apple. There is no StoreKit restore, so do not offer one.
  • That a web checkout is an in-app purchase, or that linking out to one is a permitted purchase method. Neither is true without an entitlement you do not hold.
  • Any beta, tester, device or session detail that cannot be pointed at directly.
  • That the iOS app sells digital content. After the changes above, it does not.

Still to confirm in the review notes

These live in the App Review Information notes, not in the nine answers.

  • A working demo account email and password, confirmed to stay active through the review period.
  • The devices and OS versions the build was actually opened on, replacing any example list.
  • A screen recording cut on the uploaded build, on a physical device, with no checkout sheet for digital content in it.
  • A line stating which paid flows remain on iOS: event and concert tickets, merchandise, and venue or performance bookings. Real-world goods and services, not digital content.
  • The age rating, made consistent across the rating, the audience description in answer 2 and the gating in the build.
  • The beta wording, so the notes describe the same informal testing as answer 4 instead of a TestFlight programme.
  • Confirmation that the old Guideline 3.1.1 reply has been removed from the app’s public files.