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 secret scanning cuts false alarms for AWS, Google and Alibaba cloud keys and adds a SpaceX detector

GitHub's 5 November 2026 secret scanning update tightens detectors for AWS, Google Cloud and Alibaba keys, relevant to teams building software with AI coding tools that can paste credentials into code.

Read ›

GitHub's Copilot code review can now be managed by API, with review effort levels and AI credit costs shown

GitHub's 6 November 2026 update lets organisations manage Copilot code review by API and see the review effort and AI credits each AI code review used, a sign AI-assisted development is becoming auditable.

Read ›

GitHub's Copilot impact dashboard now counts chat and VS Code agent use, and drops the 'passive users' label

On 6 November 2026 GitHub added Copilot Chat and the VS Code Agents window to its Copilot impact dashboard, bringing it to nine tracked experiences, and renamed 'Passive users' to 'Chat-first users'.

Read ›

Claude Code 2.1.319: a setting that denies permission prompts so AI agent runs don't stall

Claude Code 2.1.319 (6 November 2026) adds a permissions.denyInsteadOfPrompting setting and moves long MCP tool calls to the background, a sign AI-assisted development is being built for unattended runs.

Read ›

GitHub now reports how often developers act on Copilot code review comments

On 5 November 2026 GitHub added code review metrics, including an addressed rate, to the Copilot usage metrics API. For AI software development buyers, it is the first first-party number for how much AI review feedback is acted on.

Read ›

Dependabot can now keep AI agent skills and prompts up to date

GitHub's Dependabot gained Agent Package Manager (APM) support on 3 November 2026, treating AI agent skills, prompts and instructions as dependencies that need updating like any other 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