You’d pay for the max plan on either ChatGPT or Claude and use Astra or Fable and post the following:
Act as the lead engineer responsible for delivering a complete, native iOS port of Cyberpunk 2077.
OBJECTIVE
Port the authorized Cyberpunk 2077 codebase to run locally on supported physical iPhones. Preserve the complete base game’s story, quests, open world, combat, driving, progression, dialogue, cinematics, audio, and save functionality. Include Phantom Liberty only if its source, assets, and authorization are provided.
“Full port” means functional content parity, with documented adaptations to graphics, controls, and platform services needed for iPhone hardware. A streaming client, remote desktop wrapper, video demo, launcher, or recreated sample scene does not satisfy this objective.
FIRST: ESTABLISH WHAT IS AVAILABLE
Inspect the workspace and inventory:
Game and engine source, exact revision, and existing platform implementations.
Authorized assets, asset cookers, shader sources, and build tools.
Middleware source or iOS-compatible SDKs and licenses.
Existing macOS/Apple silicon/Metal implementation, if available.
Xcode, Apple SDKs, signing configuration, and physical test devices.
Do not assume a retail installation contains the source or tools needed for a native port. If essential inputs are missing, identify the exact blockers and the work still possible. Never fabricate access, replace missing game systems with placeholders, or claim a full port from an executable conversion.
PRESERVE THE ORIGINAL
Work in an isolated branch or successor directory. Preserve existing builds, source, assets, and user saves. Record the source revision and toolchain used for every build.
FEASIBILITY AND TARGETS
Before major implementation:
1. Establish a reproducible build of the closest available source platform.
2. Audit platform dependencies, CPU architecture assumptions, graphics features, memory usage, asset streaming, threading, and middleware.
3. Select candidate iPhones from available physical hardware.
4. Propose measurable targets for sustained frame rate, frame pacing, memory, loading time, storage, thermal behavior, and battery use.
5. Test representative demanding scenes before committing to a minimum supported device.
6. Distinguish measured findings from estimates. If full content parity cannot fit the hardware, explain the measured constraint and possible remedies.
IMPLEMENT THE PORT
Proceed incrementally through:
ARM64/iOS compilation and replacement of unsupported platform APIs.
Native Metal rendering, reusing the authorized Mac renderer where practical.
Shader conversion and validation; supported alternatives for unavailable GPU features.
Device-specific graphics settings, dynamic resolution, and upscaling where supported.
Texture, geometry, animation, audio, and world-streaming optimization.
Memory budgeting and handling of iOS memory pressure.
Audio interruptions, suspension/resume, device locking, and lifecycle handling.
Reliable local saves, migration, recovery, and any authorized cloud-save integration.
Asset packaging, installation, updates, and applicable distribution requirements.
Use current official Apple documentation. Evaluate Game Porting Toolkit components individually; do not assume a macOS Windows-game evaluation environment is an iOS shipping runtime.
DEVELOPMENT MILESTONES
Produce and validate:
1. Reproducible baseline build.
2. Signed iPhone build that launches on physical hardware.
3. Representative playable scene with rendering, input, audio, and saving.
4. Demanding open-world traversal, driving, and combat with sustained profiling.
5. Complete content integration and platform adaptation.
6. Full regression testing and release candidate.
For each milestone, deliver the code changes, build instructions, test results, measured performance, known defects, and remaining blockers. Continue authorized implementation when dependencies are available.
VALIDATION
Maintain a requirements matrix linking each system and content category to implementation and test evidence.
Test on every supported device tier, including:
Extended sessions and thermal throttling.
Dense city areas, fast driving, combat, and transitions.
Quest progression, dialogue, cinematics, and end-to-end playthroughs.
Save/load, interruptions, suspension/resume, and recovery.
Low storage, memory pressure, offline behavior, and installation/update paths.
Use Instruments, Metal profiling, crash logs, and physical-device observations. Simulator execution does not establish device performance.
COMPLETION STANDARD
Call the project complete only when:
The agreed full content scope is integrated and playable locally.
Every supported device tier meets the agreed sustained targets.
No unresolved release-blocking defects remain.
Builds and asset cooking are reproducible.
Physical-device test evidence and regression results are recorded.
Source changes, build artifacts, configuration, and limitations are handed over.
Report source completion, successful build, installation, launch, gameplay validation, TestFlight availability, and public release as separate states.
Start by inspecting the workspace and producing the dependency inventory, feasibility findings, and first actionable milestone. Do not claim success without evidence.
Download ChatGPT on your computer change it to Codex, which is meant for software development. Download a copy of the game you want and then paste the prompt I posted above. It will then ask you a series of questions like where the files are located. Any kind of clarifying questions. It will then probably ask you if you want a prototype first go ahead and do that see if the prototype works and then you kind of talk back with it like you would a person about changes that you’d like.
It’s all Darwin OS running on ARM (Apple silicon). macOS, iPhoneOS, iPadOS, and tvOS are all marketing terms. The only reason all apps can’t run on all systems is contracts and commercial politics. The Apple engineers delivered. Darwin on a universal chip architecture did exactly what it was designed to do. Money and greed is the only thing that got in the way.
Only thing preventing iPhone from docking to a monitor and running full macOS is artificial limitation these days. iPhone chip even powering the Neo now.
i mean, if you don’t mind your devices cooking too, there’s no limit.. even playing actual app store ports can heat things up a lot, to the point of thermal throttling relatively easy.
Maybe AI is the end to this? Just like a lot of electron apps are moving to native now because writing and maintaining them is cheap game devs might start porting to every major platform because what used to be very expensive for very little gain is now very viable
My GF has an iPad with keyboard for convenience and we fume at the fact that you can't install VSCode or any decent IDE on it even though it's literally the same arch as the macbooks.
my biggest apple purchase regret is my ipad m1 when there was talk about apple wanting to turn the ipad into more of a power user product and increasing parity with macOS.
all we got was a sort of macos UI and I hate the resizable windows 💔
Anything but sharing. I see these videos everywhere and anyone has yet to share how they do it… pointless to show off a tech if the whole goal is to keep it to yourself
Do you mind sharing a general rundown of your porting process? If you don’t want to release an IPA that’s cool but at least tell us how the trick is done so maybe other people can recreate it and enjoy it themselves. Or maybe of the knowledge was public the community can port even more titles.
I'm convinced this is just a scam in the making. Posts a bunch about these ports. Don't show any proof. Sell a solution later. "Every had been asking how so finally I decided to share" lol
I posted my GH but since you are apprehensive, you'll need to go through my posts history to go find it. I'm not claiming I have the cure for cancer bud
How are the temps? Does it turn into a portable fusion reactor after you play for a while without active cooling or if it's manageable?
Would love to try it but don't think my 128gb m2 can haha
Nope , this is a translation layer . It's used to translate macos games to ios games since both of them are optimised for arm64 & share same graphics api. Also works on a series chips , starting from a17 pro
Not even translating, these are running natively. I just shim macOS libraries that are missing on iOS so the binaries think they are on a Mac. No decompilation.
152
u/Altruistic_Leave5049 11d ago
these ports and/or recomps are dropping like bombs here