Develop on Windows
Write, debug and run your Flutter app exactly as you do now. Nothing about your local setup changes.
Easiest way
Just ask Claude Code
You do not have to learn any of this. Describe your app in plain words: your AI assistant writes the code, Odevio builds and signs it on a real Mac, and whatever breaks along the way gets fixed for you. No Mac, no Xcode, no iOS jargon.
Put my app on my iPhone
On it — building on a Mac now. I’ll fix anything that breaks and tell you when it’s ready.
Ready in three lines
Open your terminal and paste these once:
pip install odevio odevio signup odevio skill install
Already have an Odevio account? Use odevio signin instead of signup.
Where Windows stops, and why
Flutter is genuinely cross-platform on Windows. You can write the whole app, run it on Android, on Windows itself and in Chrome, and never hit a wall. Then you run a release build for iOS and Flutter tells you it needs Xcode. Xcode is macOS only, and macOS is licensed to run on Apple hardware only, so no amount of configuration on your PC will fix it.
Developers usually respond in one of three ways: buy a second machine purely for releases, try to virtualise macOS on the PC, or hand the iOS release to a colleague who owns a Mac. The first is expensive, the second breaks Apple’s terms and tends to break again at the next Xcode update, and the third turns one person into a bottleneck.
The fourth option: borrow a Mac only for the build
Your PC never needs to become a Mac. It only needs a Mac to be available at the moment the iOS build runs. Odevio keeps that fleet of Macs, provisions one when you ask for a build, installs your signing assets, compiles your Flutter project and releases the machine afterwards.
From the Windows side this is a single command or a single click. You stay in your usual editor, your usual terminal and your usual Git workflow.
What this looks like day to day
-
-
Build on a real Mac
Odevio runs the iOS build on Apple hardware, so the signed output is a normal iOS app with no emulation caveats.
-
Install or publish
Take the IPA for device testing, or send the build to TestFlight and the App Store without touching App Store Connect by hand.
-
Reach Xcode when you must
Some settings only exist in Xcode. A configuration build opens a remote desktop on one of our Macs so you can change them, then get back to Windows.
Three commands from a Windows terminal
$ pip install odevio
$ odevio signup
$ odevio build start --build-type configuration
Prefer a graphical tool? The Odevio desktop app runs natively on Windows and drives the same builds.
What Windows developers ask first
-
Can Flutter build for iOS on Windows?
Flutter runs on Windows, but the iOS build step needs Xcode on macOS. Odevio runs that step on a remote Mac, so from your side it works from Windows.
-
Do I need a macOS virtual machine on my PC?
No. Virtualising macOS on non-Apple hardware also breaks Apple’s licence terms. Odevio uses genuine Macs instead.
-
Do I still need an Apple Developer account?
Yes. A paid Apple Developer Program membership is required to sign apps and to distribute through TestFlight or the App Store.
-
Can I put the app on an iPhone from Windows?
Yes. An ad-hoc build produces an installable IPA, and a publication build uploads to TestFlight so your testers install it themselves.
Start building today
Install the CLI, create your account and launch your first iOS build. Every new account starts with a free trial, no Mac and no credit card needed to try it.
$ pip install odevio