DLdlahoda·Apr 25, 2026Submission
Swift-bridge facilitates Rust and Swift interop
2 points · Open discussionchinedufn
swift-bridge
Rust2021–2026
chinedufn / swift-bridge
swift-bridge
swift-bridge facilitates Rust and Swift interop.
6Distinct people
7Mentions
0Explicit recommenders
1.2KGitHub stars
What to know before exploring
What it is
swift-bridge facilitates Rust and Swift interop.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year7 dated mentions
Observed mentions: 2021-12-28 23:20:24 UTC to 2026-04-25 17:38:16 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
7 sourcesThe article provides a very detailed exploration of all of the fun challenges you can face designing FFIs with Rust, but there's a good chance you can "get away" with simpler approaches if you think ahead a bit.
In our case, we call into Rust from Kotlin using JNI [0] and Swift using swift-bridge [1]. Thankfully our use case for the FFI [2] is for non-performance-critical calls and the data structures are fairly simple, so we just serialize objects with JSON.
No major issues so far.
One thing I am surprised hasn't been mentioned so far is Mozilla's UniFFI [3] which seems to solve some of the issues brought up in the article. We plan to switch to that once our FFI requirements become more complex.
[0] https://docs.rs/jni/latest/jni/
[1] https://github.com/chinedufn/swift-bridge
[2] https://www.firezone.dev/kb/architecture/tech-stack#client
Read the rest
A bit late, but swift-bridge (https://github.com/chinedufn/swift-bridge) does this intelligently, and is probably what you're looking for.
In macOS Apps in RustGot it - the other way is actually fine because Swift does have a stable ABI - swift-bridge [1] allows interop in terms of high level types instead of devolving to C.
[1]: https://github.com/chinedufn/swift-bridge
In Apple announces full Swift rewrite of the Foundation framework (2022)Swift-based interop would provide richer type information. See how swift-bridge takes advantage of it:
https://github.com/chinedufn/swift-bridge
In Apple announces full Swift rewrite of the Foundation framework (2022)Swift-bridge: Call Rust from Swift and vice versa
4 points · Open discussionSwift-bridge: Call Rust from Swift and vice versa
6 points · Open discussion