ios-app-playbook

Use when auditing a prepared iOS release for App Store or TestFlight submission risk, including metadata, privacy, capabilities, and reviewer-facing behavior.

Use when producing App Store screenshots from real app renders instead of faked CSS mockups, covering the headless simulator export stage, the composition-to-device-sizes stage, and the gotchas that quietly waste hours. Pairs with ios-app-store-optimization, which covers what the screenshots should say.

Use when designing or reviewing an iOS app icon, lightweight brand system, launch assets, screenshot consistency, or App Store-facing visual identity choices.

Use when shaping the conversion strategy for a real iOS App Store listing: positioning, metadata, the listing promise, and the message each visual asset must convey.

Use when establishing or auditing the Apple-platform baseline for an iPhone or iPad interface, especially native conventions, system constraints, and HIG-aligned decisions.

Use after an iOS screen or flow works, when its visual execution, tactile feedback, or optical consistency still feels unfinished.

Use when designing iOS settings screens and trust-sensitive flows involving sync, restore, storage, imports, exports, destructive actions, permissions, and any wording that could cause user confusion or data loss.

Use when coordinating the end-to-end release sequence for a prepared SwiftUI app, from final verification through TestFlight or App Store submission.

Use when composing a new or materially changed SwiftUI product screen or flow that needs clear hierarchy, state ownership, and a focused user journey.

Use when submitting an App Store featuring nomination in App Store Connect (Featuring -> Nominations) for an update, launch, or in-app event, including how to write each field, when to time it, and what realistic expectations to hold.

Use when you want to archive, sign, export, and upload an iOS App Store build in one command, or when a build is missing from App Store Connect and you need the local archive-to-upload step automated. Complements solo-ios-release-flow, which holds the judgment and the checklist; this skill is the automation underneath it.

Use when auditing an iOS interface for accessibility, including Dynamic Type, contrast, VoiceOver clarity, hit targets, reduced motion, and interaction patterns that need to remain usable for a wider range of people.

Use when adapting an iOS app across iPhone and iPad, handling safe areas, readable widths, compact versus regular size classes, split layouts, and SwiftUI structures that need to stay native across device contexts.

Use when designing onboarding, first-run, zero-state, or no-data experiences for iOS apps so people understand what the product does, what to do next, and how to reach value quickly without heavy setup friction.

Use when designing or reviewing iOS forms, text fields, pickers, validation, keyboards, grouped form layouts, save flows, or any input-heavy screen that needs to feel cleaner and easier to complete on iPhone.

Use when refining iOS interaction polish, including subtle motion, haptics, transitions, state feedback, loading behavior, and microinteractions that should feel native instead of flashy or delayed.

Use when deciding how an iPhone or iPad app should be organized, including tab bars, drill-down flows, sheets, settings grouping, information architecture, and navigation patterns that should feel native on iOS.

Use when starting a new native iOS app, reshaping an existing SwiftUI codebase, or deciding how to structure screens, models, services, persistence, extensions, and app-wide conventions for fast solo shipping.

Use when an iOS app is crashing, hanging, misrendering, failing tests, or showing warnings around SwiftUI state, SwiftData, concurrency, entitlements, simulator/device differences, or App Store submission stability.