Let’s be honest for a second. Apple’s official iOS Simulator has always been a bit of a joke. Sure, it’s fine if you’re tapping buttons in Xcode, but the second you try to do anything actually interesting—like poke around the real OS internals, test bare-metal performance, or run the thing outside of Apple’s sterile developer playground—you hit a brick wall. Cupertino loves giving us sandboxes, but they always make damn sure they hold the key to the gate.
Well, somebody finally picked the lock.
A developer recently dropped a project called vphone-cli, and it’s causing absolute chaos in the tech underground. What does it do? It casually lets you boot a literal, virtual iPhone on your Mac using Apple’s own built-in Virtualization.framework.
Let that sink in. Apple spent years telling us that running actual iOS in a proper virtual machine outside their locked-down tools was either impossible or reserved for their own internal labs. Turns out, the tools to do it have been quietly chilling right inside macOS the whole time. All it took was someone with enough stubbornness and terminal skills to wire them together.
When I first saw this, I laughed out loud. This is the ultimate “it’s not a bug, it’s a feature” middle finger to Apple’s walled garden. For years, the jailbreak community has begged for this level of deep access, and tinkerers have dreamed of running real iOS instances without needing a physical device tethered by a frayed USB-C cable. Now, thanks to a clever implementation of a native macOS framework, we’re looking at iOS running in a window like it’s just another Linux distro in UTM.
Of course, the corporate stiffs are going to hate this.
Apple’s entire business model relies on hardware exclusivity and software control. They want you buying multiple devices, keeping your workflow tethered to their ecosystem, and playing strictly by their rules. Giving developers and power users the ability to spin up a headless, virtual iPhone instance on a beefy Mac Studio fundamentally disrupts that control freak dynamic. What happens to device testing farms? What happens to security research when anyone with a Mac can spin up an instance of iOS in seconds?
Predictably, the usual suspects in the tech press are clutching their pearls. Is it legal? Does it violate some obscure clause in the Developer Agreement? Will Tim Cook personally come to your house and take away your M-series MacBook?
Spare me.
We are talking about hardware and software that we paid for. If I buy a Mac, I should be able to run whatever the hell I want on its hypervisor, using the APIs Apple themselves provided in the OS. The fact that we have to rely on open-source GitHub repos just to do something as basic as virtualization of Apple’s mobile OS on Apple’s desktop OS is a symptom of how locked-down personal computing has become. We’ve been conditioned to accept handcuffs as a “security feature.”
This tool proves that the walls of the walled garden are built on duct tape and software flags. The framework was right there. The capability was dying to be unlocked.
Here is my hot take: vphone-cli isn’t just a cool weekend project for nerds; it’s a terrifying preview of a future Apple wants to outlaw. Enjoy it while it lasts, because the second this gains enough mainstream traction, you can bet Apple will patch the loophole, claim it’s a “critical security vulnerability,” and pretend this level of user freedom was never meant to exist.