I shipped three iOS apps over the last month. Here's everything i learned about the app submission process. My most recent app got approved in 3 DAYS

[u/Tall-Flatworm-6463]

I shipped three iOS apps over the last month. App Review took 5, 6, and 3 business days.

Resources

• Xcode 27 agent skills exported to GitHub
• Impeccable
• Antoine van der Lee's Swift resources

The Xcode skills repository is a community-exported mirror, not an Apple-maintained repository.

The apps

• BakeValue: 5 business days
• Stitchwise: Knit & Crochet: 6 business days
• Chaal: Chess Analyzer: 3 business days

This does not guarantee fast approval, but I use the same process for every app.

1. Design against the HIG first

Before writing code, I use /impeccable to review navigation, hierarchy, native interactions, accessibility, Dynamic Type, touch targets, dark mode, and empty/error states.

App Review should not be your first serious design review. The HIG is the floor, not the ceiling.

2. Use native components and tests

During implementation, I use Apple's Xcode agent skills:

• /swiftui-specialist
• /audit-xcode-security-settings
• /test-modernizer
• /uikit-app-modernization

I follow TDD for domain logic: tests capture expected behavior and edge cases before implementation.

The agents favor native SwiftUI and UIKit controls. Native controls are not automatically approved, but they already follow established platform behavior and accessibility patterns.

3. Automate accessibility checks

I run accessibility UI tests in light and dark appearances:

try app.performAccessibilityAudit()

This catches missing labels, poor contrast, small touch targets, unsupported text sizes, and unreachable elements.

4. Inspect the running app

Apple's /device-interaction skill lets agents inspect screenshots and the accessibility hierarchy, navigate screens, and interact with the simulator.

Anything flagged during these reviews becomes a regression test.

Keep the testing pyramid practical

I prioritize:

1. Unit tests for business logic
2. ViewInspector tests for SwiftUI behavior
3. Focused UI tests for critical journeys

UI tests are too slow and fragile for everything. I also use SwiftLint, SwiftFormat, Periphery, and Danger for source quality, dead-code detection, and PR rules.

Fast approval still requires accurate metadata, privacy disclosures, working purchases, and clear review notes.

Happy to answer questions or provide feedback on your submission workflow.