Updates ·

What comes after the proof of concept

The planned order of work for Xwift, from a single CLI to mobile targets, a UI framework and system APIs. Plans, not promises.

By Teodor Walter Vido

With one package built for four targets, the question is what to build next. This post lays out the intended order. Everything here is planned: none of it exists yet, and the order may change as we learn.

1. The xwift CLI

Today, building for each target means remembering a different incantation: a toolchain installer here, an SDK flag there, a separate runtime for WebAssembly. The first planned piece of Xwift is one command that hides that:

Planned (not yet available)
xwift new MyApp
xwift build --target windows
xwift run --target web

The CLI is meant to manage pinned toolchains and SDKs per project, the same way the proof of concept pins Swift 6.4.1 and checksums the WebAssembly SDK.

2. Android and iOS

Mobile targets are on the roadmap but have not been built yet. They come after the CLI because they need the most toolchain and packaging glue: SDKs, signing, emulators and device runners.

3. UI framework and system APIs

A declarative UI layer that renders natively on each platform, and portable system APIs for files, networking, windows and devices. These are the largest pieces of work and the furthest out.

4. Performance and tooling

Performance work and AI-assisted tooling are on the list too, but we will not publish numbers or claims until there is something real to measure.

How we will report progress

Each step lands here as a post when there is a real build behind it. Nothing will be called released before it is.