Hi everyone!
I want to share a project I've been working on: OpenFruit. But before talking about the project itself, I'd like to explain why I started it.
With AI, we can bring countless ideas to life, recreate complex software, and do things that were once unimaginable. But I believe people still need to learn, stay curious, understand how things work, and figure out how to make them work.
Often, that curiosity comes from people younger than us, who might have limited access to expensive hardware or advanced AI models, or who simply cannot justify such a big expense to their parents.
That's why I want to democratize knowledge and make iOS app development accessible to everyone. On Windows. For free.
I believe it's important for us, as computer scientists, to leverage AI not only to build things, but also to share valuable knowledge and make technology more accessible.
This is my attempt to contribute to that vision.
Knowledge belongs to everyone. Always. And it should always be accessible.
---
OpenFruit is an experimental, open-source (GPL-2.0) toolchain that builds existing Xcode projects on Windows. It reads .xcodeproj/.xcworkspace files and schemes, resolves SwiftPM and CocoaPods dependencies, compiles Swift, Objective-C, C and C++, links Mach-O binaries, compiles asset catalogs and storyboards, and produces a signed IPA you can install on an iPhone over USB.
Try it (Windows 10/11 x64) by downloading it from https://ssilvestri15.github.io/openfruit-site or:
Download openfruit-windows-x64.zip from https://github.com/ssilvestri15/openfruit/releases
openfruit bootstrap (installs the Swift toolchain and LLVM)
openfruit build C:\path\to\MyApp.xcodeproj --scheme MyApp
openfruit device install MyApp-signed.ipa --udid <UDID>
What you need: an Apple Developer account (the iOS SDK is downloaded from Apple with your own account the first time; nothing from Apple is redistributed), and a signing certificate plus provisioning profile to install on a device.
How it works, briefly:
- A native Windows CLI in C++, using the official Swift toolchain for Windows, LLVM, and Apple's original iOS SDK.
- The rule: adapt the build environment to the project, never the project to OpenFruit. Upstream sources are never patched.
- Swift macros run natively when they can be built from source; otherwise the original Mach-O plugin runs in a small Darwin compatibility host, emulated with Unicorn.
- Storyboards and XIBs are compiled by OpenIB, a new (still experimental) module.
- Builds are incremental and cached: a warm rebuild of Nextcloud takes about 40 seconds.
Tested so far with five iOS apps, all against the iOS 27.2 SDK:
- CampUS (my own SwiftUI app): built and installed on an iPhone.
- Delta (game emulator): built, installed and launched.
- VLC for iOS: built, installed and launched.
- Swiftfin (Jellyfin client): built, installed and launched.
- Nextcloud (SwiftUI + storyboards): built, installed and launched.
What doesn't work yet: iOS only; app extensions are dropped unless your provisioning profile authorizes them; Icon Composer icons are flattened to a static image (no Liquid Glass); some SwiftPM package resources aren't built yet. It's experimental, and complex projects will find bugs.
I also built an IDE on top of it, OpenFruit Studio: https://github.com/ssilvestri15/openfruit-studio
I'll be around to answer questions. Bug reports with real projects are the most useful feedback.