Checklist for Adding Controllers
This appendix summarizes the critical issues described in this document by providing two checklists, one for iOS and one for Mac.
iOS Checklist
iOS Requirements
Your game must not require a game controller. | |
Your game must be playable using a standalone controller, without access to the device. | |
Your game must support the pause notification. It should toggle between pausing and resuming your game. | |
Your game must disable the screen idle timer if the touchscreen is not used in your gameplay. See the | |
When the iOS device is placed inside a formfitting controller, your game must run only in landscape mode. | |
Your game must hide any virtual controls while it is being controlled from a controller. | |
After a controller is connected, set the player index to a reasonable value. |
iOS Recommendations
Provide a user interface that explains which control elements are used by your game. Use the standard names for control elements. | |
Respond appropriately when a controller is connected or disconnected. | |
Make a control layout that is easy for players to understand and operate. | |
Remove any code from your app that compensates for thumbstick dead zones. | |
When using button elements, use the |
tvOS Checklist
tvOS Requirements
Your game must support the Siri Remote or an MFi Game Controller. (It may support both.) | |
Your game must support the pause notification. It should toggle between pausing and resuming your game. When your gameplay is inactive, you should ignore inputs in the Game Controller framework so that this button is processed appropriately by UIKit. | |
Your game must disable the screen idle timer if a controller’s input is being used directly. See the |
tvOS Recommendations
Provide a user interface that explains which control elements are used by your game. Use the standard names for control elements. | |
After a controller is connected, set the player index to a reasonable value. | |
Respond appropriately when a controller is connected or disconnected. | |
Make a control layout that is easy for players to understand and operate. | |
Remove any code from your app that compensates for thumbstick dead zones. | |
When using button elements, use the |
OS X Checklist
OS X Requirements
Your game must not require a game controller. | |
Your game must be playable using a standalone controller, without access to the Mac. | |
Your game must support the pause notification. It should toggle between pausing and resuming your game. | |
After a controller is connected, set the player index to a reasonable value. |
OS X Recommendations
Provide a user interface that explains which control elements are used by your game. Use the standard names for control elements. | |
Respond appropriately when a controller is connected or disconnected. | |
Make a control layout that is easy for players to understand and operate. | |
Remove any code from your app that compensates for thumbstick dead zones. | |
When using button elements, use the |
Copyright © 2016 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2016-09-13