Swift can now officially target Android — a fourth cross-platform option

Swift 6.3, released in March 2026, ships an official first-class Android SDK, and the Skip framework that bridges SwiftUI to Jetpack Compose went fully open source in January — giving iOS-first teams a real option for reaching Android without Flutter, React Native or Kotlin Multiplatform.

Swift 6.3 shipped in March 2026 with an Android SDK positioned alongside Static Linux and WebAssembly as a first-class, officially maintained target — not an experiment. The Swift on Android Working Group, founded in early 2025, was promoted to an official Swift Platform Steering Group workgroup as the effort moved from preview builds to production. Over 2,200 Swift packages already build for Android. Separately, Skip — the framework that compiles Swift and SwiftUI into native Jetpack Compose for Android from a single codebase — went fully open source in January 2026 after three years as a licensed product.

Why this changes the cross-platform conversation

Until now, a team building natively for iOS in Swift and SwiftUI faced a real rewrite to reach Android: a second codebase in Kotlin, or a jump to Flutter or React Native with its own learning curve and trade-offs. Skip on top of official Swift-for-Android support means an iOS-first codebase can now target Android with no separate runtime and no second language, which is a materially different proposition than Kotlin Multiplatform (which shares logic but not UI) or Flutter/React Native (which mean starting over in a different language). This sits alongside — not above — the frameworks we’ve already covered: Flutter still leads adoption at roughly 46% market share, and React Native’s new architecture is now stable in production. Swift-for-Android is younger and its ecosystem is thinner, but it closes a gap that mattered specifically for teams already committed to native Swift.

So what

For founders who started with an iOS app and are now weighing how to reach Android, this adds a genuine fourth option to the shortlist rather than forcing a binary choice between “stay native and build twice” or “go cross-platform and rewrite.” Which route makes sense still depends on the app, the team, and the timeline — that’s a conversation worth having before committing to a stack. See how we approach these trade-offs on our services page, or get in touch to talk through your specific build.

← All research

More research.

GitHub's Copilot metrics now count OpenCode and Claude Code traffic: who really uses which AI coding tool

On 23 October 2026 GitHub added a per-tool breakdown to the Copilot usage metrics API, so tools such as OpenCode and Claude Code are counted even without editor telemetry. It shows how mixed the AI coding tool stack inside software teams has become.

Read ›

GitHub Copilot retires Claude Opus 5 and GPT-5.6 Terra on 16 November: the model-churn bill for buyers

GitHub has announced that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave every Copilot experience on 16 November 2026. For anyone commissioning AI-assisted development, model retirement is now a monthly event to plan around.

Read ›

GitHub Copilot now benchmarks how 'agent-first' your developers are against your industry

On 22 October 2026 GitHub added opt-in industry comparisons to its Copilot impact dashboard, ranking firms by share of agent-first developers and by the merge rate of agentic pull requests. Here is how to read the numbers when you are buying software.

Read ›

Apple's new bait-and-switch rule 2.5.19: what it means for AI-built and fast-shipped apps

On 16 October 2026 Apple updated its App Review Guidelines: apps that change after approval can be removed from the App Store and the Developer Program, and AI-generated intimate imagery is now explicitly covered. Here is what founders commissioning an iOS app should check.

Read ›

GitHub Copilot agentic autofix is generally available: AI now fixes security alerts, and bills for it

GitHub made agentic autofix for code scanning alerts generally available on 15 October 2026. Copilot can now fix up to 25 security alerts in one pull request, using AI credits your supplier or your team pays for.

Read ›

GitHub AI Scan for pull requests goes GA: AI security checks for PHP, Terraform and Dockerfiles

GitHub's AI Scan for pull requests became generally available on 15 October 2026, checking languages the standard scanner misses. Findings are advisory and cannot block a merge, which matters when you buy software.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work