iOS roadmap: Swift, SwiftUI, and what's next
Why iOS is coming after Android, what the output will look like, and why you'll still need a Mac.
Android first was deliberate. Here's why, and what comes next.
Why Android first#
Android has an open toolchain: every OS can build it, the SDK is free, and signing is straightforward. iOS requires macOS, Xcode, a paid developer account, and a provisioning dance. Starting with Android let us prove the pipeline without platform gatekeeping slowing the work.
What iOS output will look like#
Native Swift + SwiftUI. Same philosophy as Android: no React Native, no Flutter, no WebView. The generated project opens in Xcode and looks like code an experienced iOS engineer wrote.
Yes, you still need a Mac#
Every iOS toolchain on earth requires macOS for the final build and signing. That's a platform rule, not ours. The good news: your existing Apirex project (web spec, designs, auth detection) carries straight over — only the build host needs to change.
Code sharing#
Compose Multiplatform is on our radar for shared logic and theming. UI stays platform-native because that's the whole point of Apirex.
When#
iOS beta is targeted for Q3 2026. Toggle iOS interest in your dashboard and we'll invite the early-access cohort first — or join the waitlist.
Keep reading
All articles →
Hello, Apirex.
The world doesn't need another app builder. It needs a way to give every existing website a real native life. That's what we're building.
Why real native beats a WebView every single time
WebView wrappers ship your website inside a browser. Apirex generates real Kotlin. Here's why that difference is everything.
Apirex vs Lovable, Bolt, Replit, and AI assistants — where we're better
AI coding tools are exploding. Here's an honest, side-by-side look at why Apirex wins for shipping a real native mobile app.