Check device requirements

Prerequisites: check the play device first

Use the chip and operating system together. A product name that sounds newer is not a substitute for checking its chip. These are the nxnative README’s baseline requirements at the source check date; they are not a performance rating.

Target	Documented starting requirement	Still needs checking
iPhone	A17 Pro or later; iOS 26 or later	Exact game version and iPhone evidence
iPad	M1 or later; iPadOS 26 or later	Exact game version and iPad evidence
Mac app	Apple silicon; the mac-app build target	The chosen profile and your Mac environment

The upstream explanation for the mobile chip requirement is BC-compressed textures. Do not assume that installing a newer OS removes a chip limitation. In particular, the ordinary iPhone 15 is not the iPhone 15 Pro.

Separate the build Mac from the play device

The documented workflow builds on a Mac with Xcode and Homebrew. The upstream setup instructions maintain the current dependency commands. Complete that setup before interpreting a missing-tool error as a game compatibility failure. The Mac app itself needs Apple silicon; do not turn the ability to prepare files into an Intel gameplay claim.

Keep the terminal output from dependency setup and the nxnative revision together. If a command is missing, finish the corresponding upstream setup step before retrying the game build. This site does not run that setup on your machine.

Prepare the game inputs and working space

1. Put one game’s own base files and matching updates in a dedicated folder. Include only the DLC you intend to use.
2. Keep your own prod.keys in a known location; it is an input to the build, not something to upload here.
3. Read the game’s profile for its tested version and limitations. A version that packages is not automatically the tested version.
4. Check free space on the volume containing the inputs and build output. Account for the extracted game, build intermediates and final app; an output file’s size alone is not a storage budget.
5. If using compressed inputs, allow for the decompressed files as well. Follow the current README’s compressed-input instructions.

Keep an existing build and a separate save backup until the replacement is checked. Do not reclaim space by deleting your only working app or only save copy.

Mobile installation needs another check

An IPA is a build artifact. You still need an installation method and a signing configuration that your device accepts. The upstream README discusses the Increased Memory Limit capability when the chosen signing tool supports it. Availability is not automatic, and enabling it is not a universal crash fix. Follow the tool’s current instructions rather than copying an unrelated entitlement recipe.

Use the iPhone/iPad installation guide to keep build, signing, installation and first launch separate. A failure at one stage should not send you back to repeat every earlier stage.

Checkpoint: ready to proceed?

You should be able to name the target device and OS, game version, nxnative revision, input folder and expected output type. If any item is unknown, resolve it before a long build. Continue with quick start, Mac app build or mobile installation.

If your device does not meet nxnative’s documented baseline, stop this route. The project comparison explains why another project’s requirements must be evaluated separately; it is not a way to override nxnative’s requirements.