NX2Apple: One-Click Switch Games on iPhone, No Terminal

What NX2Apple adds

NX2Apple is not a new engine. It is a fork of nxnative that keeps the hard parts upstream — the code rewriter, the Horizon host layer, the NVN-on-Metal translation, the per-game profiles — and adds two things on top.

A GUI. NS Port Builder takes four inputs (base game, update, DLC, keys), detects the dependencies on your Mac and installs what it can, shows the build's own stage-by-stage progress, and ends with an install guide and Reveal-in-Finder buttons. It also clones the repository for you and updates itself, so no git knowledge is required.

An archive format. This is the more interesting half, and it solves a real wall: some games are too many files to install as an app. Tears of the Kingdom is 304,243 files; packed into an archive it becomes 127 shards, which iOS will accept. The fork reports byte-verifying all 304,243 files against the source.

What you need

Item	Requirement
Build machine	Apple-silicon Mac, macOS 13 or later
Toolchain	Xcode with the iOS SDK, Python 3.9+, .NET SDK 10 — the app's dependency panel detects each and installs what it can
Phone	iOS 26+ and a recent iPhone. The project says older devices are untested; the engine it builds on states iPhone 15 Pro or newer, and the texture reason applies here too
Your files	Base game, update, DLC, prod.keys — nothing is bundled or downloaded
On the phone	A sideloading tool, and the increased-memory-limit capability if the game is large

The steps, as the project lays them out

1. Download the app from its releases page, unzip, right-click and Open the first time (it is not notarised).
2. Let it fetch the repository — one button does a shallow clone into your home folder. If GitHub is slow from where you are, the panel shows the manual ZIP route.
3. Pick your four inputs — base game, update, DLC and prod.keys, separately or as one folder.
4. Press build. First build is long; the build is resumable, so a stopped run continues rather than restarting.
5. Follow the three install steps it prints. That is the point where the phone-side memory entitlement matters.

Verified versus reported

This is the number to read carefully, because it is where most guides overstate things:

Status	Count	What it means
Verified end to end on this fork	3	Built, installed and played on a real iPhone. The three are Tears of the Kingdom, Hades II and Animal Crossing: New Horizons.
Reported playable upstream	29	Someone upstream says it runs. Not re-verified by this fork.
Profiles in total	58	The per-game configuration exists. It does not mean anyone finished the game on a phone.

The separate 62-game list comes from the upstream project and is a different table with a different count. Both are honest; they measure different things, and neither is a compatibility guarantee.

The limits that will actually bite

• The memory ceiling. Without the entitlement an app gets roughly 3,375 MB. Tears of the Kingdom was killed at 3,342 MB while opening the world map — 33 MB short. Lowering the render scale does not fix that, because it is a process limit, not a rendering cost.
• Handheld versus docked. The engine renders 1080p docked by default; setting DM_OPMODE=0 in Documents/env.txt switches to 720p handheld, which is the simplest way to buy headroom on a phone.
• Touch controls are a fallback. Two layouts exist (2D and 3D), but Xbox, PlayStation, Switch Pro and MFi pads all work and hide the touch layer when connected. For anything action-heavy, use a pad.
• Read-only archive. The archive is never written to; saves go to their own mount. Copy the save/ folder out before you reinstall, or a new data folder can lose your progress.

NX2Apple or nxnative

Choose	If
NX2Apple	You want the fewest steps, you are on macOS, and the game you want is large enough to need archive packing (Zelda, Animal Crossing).
nxnative	You are comfortable in a terminal, want to follow upstream directly, or intend to contribute a profile for a game nobody has done yet.
d2r-mobile	The game is Diablo II: Resurrected — and you may not need a Mac at all. Start with the install guide.

Features, requirements, counts, the memory measurements and the archive details are from the NX2Apple README and its limitations section (checked 2026-10-26), with the device floor taken from the upstream nxnative documentation (checked 2026-10-25). The comparison table and the "what will actually bite" framing are our editorial judgement.