Apple's Gatekeeping: The Struggle to Showcase My App

Currently, the primary application of Large Language Models (LLMs) is writing code. While this will likely evolve into general automation—where LLMs act as the "brain" for autonomous agents—the current era of vibe coding has significantly impacted Apple's ecosystem.

The App Store Deluge

The App Store is currently being flooded with a massive volume of apps created via "vibe coding." This shift has led to a historic milestone: non-game applications have finally surpassed games as the primary revenue driver on the platform.

This surge has placed immense strain on the app review team. While they generally maintain high quality standards, the sheer volume of submissions has broken their timeline.

The Review Timeline Gap

Apple still tells developers to expect a response within 24 to 48 hours. However, this is a relic of a simpler time. Even global giants like X are experiencing delays lasting a week or more.

The "Pressure" on the review team can be expressed as: $\text{Pressure} = \frac{\text{Volume of Vibe-Coded Apps}}{\text{Reviewer Capacity}}$

The "Automated" Rejection Experience

When I submitted the latest version of Wiseday, I managed a 3-day turnaround, but the result was a rejection that left me frustrated. It feels as though reviewers no longer write personalized feedback; instead, they select from a pre-defined menu of errors.

def apple_review_process(app_submission):
    if app_submission.has_issue():
        return select_canned_response(issue_id=402) # "Screenshots insufficient"
    else:
        return "Approved"

This creates a stifling atmosphere where the developer feels they aren't actually communicating with a human being.

The Wiseday Dilemma

I have iterated on Wiseday extensively. I finally feel the current version is the "real" app—the one I am proud to market. The hardest part has been communicating the app's value: the daily printable page.

The Conflict of Requirements

Apple rejected my latest screenshots based on the following guidelines:

Issue: The screenshots do not show the actual app in use in the majority of the screenshots.

Resources:

• Marketing materials that don't reflect the UI are inappropriate.
• The majority of images should highlight main features and functionality.
• Note: Login and splash screens do not count as "app in use."

This created a logical paradox for me. Apple's requirements were diametrically opposed:

1. Requirement A: Show the "actual app in use."
2. Requirement B: Highlight the "core concept" to show value.

Since Wiseday's core concept is a physical piece of paper, showing the "value" means showing the paper, but showing the "UI" means showing the screen.

My Path to Resolution

To fight this, I took the following steps:

• Argued that the paper images in screenshots #2 and #3 are technically part of the UI (via the page preview component).
• Added an additional traditional device-wrapped screenshot to satisfy the "majority" rule.
• Wait for a human to actually read the response.

I sincerely hope the review team considers the unique nature of an app whose primary output is non-digital.

---

Explore more:

• Wiseday Planner: Print your daily page to meet your goals.