Apple Game Platform Delivery
Own the Apple-specific boundary between a game engine or SpriteKit project and a tested, distributable iPhone, iPad, or Mac game.
Use When
- Integrating Apple game services or diagnosing Apple-only runtime, input, graphics, save, signing, or distribution failures.
- Choosing Mac App Store, direct notarised distribution, or another approved storefront.
Do Not Use When
- The task is general iOS application work; use the iOS family.
- Current Apple requirements and the pinned Xcode/OS/engine versions cannot be verified.
Required Inputs
Game/engine version, Xcode version, target OS and hardware matrix, distribution channel, bundle identifiers, entitlements, service/data map, signing ownership, save model, input/display requirements, and acceptance criteria.
Workflow
- Pin the toolchain and verify current Apple requirements from official sources.
- Define platform adapters for identity, Game Center, controllers, haptics, cloud saves, purchases, lifecycle, and diagnostics; keep gameplay independent.
- Specify Mac windowed/full-screen behaviour, Retina scaling, multi-display changes, keyboard/mouse/controller remapping, focus loss, and safe save locations.
- Test Metal-relevant failures on representative Apple hardware and retain captures with build, device, OS, scene, and conditions.
- Rehearse certificate/provisioning failure, entitlement mismatch, offline service failure, save conflict, suspend/terminate, and controller disconnect.
- Archive once, retain symbols/checksums, and promote the tested artefact through signing, hardened-runtime, sandbox, notarisation, and channel gates as applicable.
Quality Standards
- Never transplant obsolete Swift, SpriteKit, Game Center, or Xcode APIs from a book; preserve only the architectural lesson and verify the current API.
- Apple services degrade without corrupting local state or blocking offline-capable play.
- No signing key or service secret enters the client repository.
Outputs
Apple platform contract; service adapters; device/display/input matrix; entitlement and signing register; tested archive with symbols/checksum; distribution and rollback record.
References
- Apple game delivery gates
1---2name: apple-game-platform-delivery3description: Use when delivering a game on iOS, iPadOS, or macOS with Apple-native services, Metal diagnostics, controllers, haptics, cloud saves, signing, notarisation, sandboxing, or Mac window and display behaviour.4metadata: {portable: true, compatible_with: [claude-code, codex]}5---67# Apple Game Platform Delivery89Own the Apple-specific boundary between a game engine or SpriteKit project and a tested, distributable iPhone, iPad, or Mac game.1011## Use When12- Integrating Apple game services or diagnosing Apple-only runtime, input, graphics, save, signing, or distribution failures.13- Choosing Mac App Store, direct notarised distribution, or another approved storefront.1415## Do Not Use When16- The task is general iOS application work; use the iOS family.17- Current Apple requirements and the pinned Xcode/OS/engine versions cannot be verified.1819## Required Inputs20Game/engine version, Xcode version, target OS and hardware matrix, distribution channel, bundle identifiers, entitlements, service/data map, signing ownership, save model, input/display requirements, and acceptance criteria.2122## Workflow231. Pin the toolchain and verify current Apple requirements from official sources.242. Define platform adapters for identity, Game Center, controllers, haptics, cloud saves, purchases, lifecycle, and diagnostics; keep gameplay independent.253. Specify Mac windowed/full-screen behaviour, Retina scaling, multi-display changes, keyboard/mouse/controller remapping, focus loss, and safe save locations.264. Test Metal-relevant failures on representative Apple hardware and retain captures with build, device, OS, scene, and conditions.275. Rehearse certificate/provisioning failure, entitlement mismatch, offline service failure, save conflict, suspend/terminate, and controller disconnect.286. Archive once, retain symbols/checksums, and promote the tested artefact through signing, hardened-runtime, sandbox, notarisation, and channel gates as applicable.2930## Quality Standards31- Never transplant obsolete Swift, SpriteKit, Game Center, or Xcode APIs from a book; preserve only the architectural lesson and verify the current API.32- Apple services degrade without corrupting local state or blocking offline-capable play.33- No signing key or service secret enters the client repository.3435## Outputs36Apple platform contract; service adapters; device/display/input matrix; entitlement and signing register; tested archive with symbols/checksum; distribution and rollback record.3738## References39- [Apple game delivery gates](references/apple-game-delivery-gates.md)40
peterbamuhigire