Working with WebAssembly and Swift: From A to Z

Introduction to WebAssembly and Swift

WebAssembly (WASM) is a low-level binary instruction format that allows running code written in various languages (C, C++, Rust, Swift) in the browser and beyond at near-native speed. For Swift developers on iOS and macOS platforms, integration with WebAssembly opens up new possibilities: porting existing libraries, accelerating computational tasks, and cross-platform unification.

In this article, you will learn how to set up the environment, compile Swift code into WASM, and call it from a native application. We will look at practical examples and analyze typical errors.

1. WebAssembly Basics: Architecture and Advantages

WebAssembly is a virtual machine with linear memory and strict typing. Key features:

\n
• Security — isolated execution (sandbox);
\n
• Performance — near-native due to precompilation;
\n
• Compactness — the binary .wasm format takes up little space;
\n
• Integration — easily called from JavaScript, Swift, Rust.
\n

For Swift, there is the SwiftWasm project, which allows compiling Swift code into WASM. This is especially useful for creating computational modules that are then used in iOS applications.

2. Setting Up the Environment for SwiftWasm

Before writing code, install the tools. Open the terminal and run:

# Installing SwiftWasm (via Homebrew)\nbrew install swiftwasm/tap/swiftwasm\n\n# Checking the version\nswift --version

You will also need wasmtime for local testing:

brew install wasmtime

Create a new Swift package:

mkdir MyWasmApp && cd MyWasmApp\nswift package init --type executable

3. Writing and Compiling a Swift Module into WASM

Let's look at a simple example — a function for adding two numbers. Edit the file Sources/main.swift:

@_extern(wasm, module: "env", name: "add")\nfunc add(_ a: Int, _ b: Int) -> Int\n\n@main\nstruct App {\n    static func main() {\n        let result = add(5, 3)\n        print("Result: \\(result)")\n    }\n}

Now compile into WASM:

swift build --triple wasm32-unknown-wasi

After a successful build, the file .build/wasm32-unknown-wasi/release/MyWasmApp.wasm will appear. Run it via wasmtime:

wasmtime .build/wasm32-unknown-wasi/release/MyWasmApp.wasm

You should see the output: Result: 8.

4. Integrating WebAssembly into a Native iOS/macOS Application

Now for the interesting part — calling a WASM function from a Swift application on iOS. Use the WasmKit library (or WASMInterfaces).

4.1 Adding the Dependency

In Package.swift of your iOS project, add:

dependencies: [\n    .package(url: "https://github.com/swiftwasm/WasmKit.git", from: "0.1.0")\n],\ntargets: [\n    .target(\n        name: "YourApp",\n        dependencies: ["WasmKit"]\n    )\n]

4.2 Loading and Calling the WASM Module

Example code for loading a .wasm file and calling a function:

import WasmKit\n\nfunc callWasmAdd() throws {\n    guard let wasmURL = Bundle.main.url(forResource: "MyWasmApp", withExtension: "wasm") else {\n        fatalError("WASM file not found")\n    }\n    let wasmData = try Data(contentsOf: wasmURL)\n    let engine = WasmEngine()\n    let module = try engine.loadModule(wasmData)\n    let instance = try module.instantiate()\n    \n    // Calling the add function\n    let result = try instance.exports["add"]?.function?.call([5, 3])\n    print("WASM result: \\(result?.first ?? 0)")\n}

Don't forget to add the .was