Repository navigation
Windows support or a Windows-compatible alternative? #455
Replies: 2 comments
|
get a Mac. The audacity you have to ask such a question is beyond me. and if you really cant get a Mac then buy a claude subscription and get to work instead of hoping someone does the work for you. |
|
in a less harsh way, no. vphone uses a Mac-specific feature in the virtualization framework called the private cloud compute virtual research environment (VRE). it basically abuses the fact that PCC's cloudOS is an iOS fork, allowing (with lots of hacks and patches) iOS itself to boot without having to build an entire hypervisor from scratch. vphone is NOT a hypervisor by itself, and it probably never will be. there are some QEMU forks capable of emulating apple silicon, so you're not entirely out of luck. though you would most likely be stuck with old versions of iOS. note also that windows pcs are typically amd64/i386 so performance will be terrible, and there's nothing that can be done in that regard. iOS has always been (and remains) arm. the reason why apple silicon macs can virtualize is because they are also now arm, just like iphones and ipads have been. sidenote: i also don't think Claude would get you very far in this regard |
Uh oh!
There was an error while loading. Please reload this page.
Hi! This project looks extremely useful, and I would like to use it for testing my own apps and services. However, my main development machine runs Windows.
I understand that vphone-cli currently depends on Apple Silicon, macOS, and Apple’s Virtualization.framework. Is native Windows support technically possible in the future, or do these dependencies make it fundamentally impossible?
If native virtualization on Windows is not feasible, would you consider a Windows client that remotely controls vphone-cli running on a Mac? For example, it could manage VMs, change simulated locations, install IPA files, and access the screen remotely.
Are there any plans or recommended solutions for Windows users?
All reactions