IOS app?

[mus2go]

Hello I just recently found this on F-droid I'm quite amazed. I kinda was asking myself why something like this didn't exist sooner.

I wanted to ask if there is gonna be an IOS version since there is a huge user base.
https://youtu.be/L0JQgZucb0c
Also found this vid maybe it's useful. :)

[zaventh]

Thanks for the comments.

I want an iOS version and designed the protocol so one is possible. I just can't write it right now: I don't own any modern Apple hardware, so no Mac, no Xcode, no device testing. That's the main blocker.

The design side is done. docs/IOS_PORT_REVIEW.md has the detail, and a few things shipped in the Android app specifically to keep the door open: de-Tinked crypto (raw keys that map straight onto CryptoKit), an Apple-conformant Wi-Fi Aware service name, and golden vectors a Swift codec can reproduce byte for byte.

Two real limits, though. Wi-Fi Aware won't work cross-platform: Apple requires PIN pairing per device pair, exposes no NAN follow-up messaging, and offers no raw-PSK data path. There's no "connect to whoever is running the same service", which is the entire premise of a stranger mesh. So iOS would be BLE-only, which CompositeMeshTransport already handles — an iPhone would just look like a BLE-only Android phone.

Background is the other one, and it's usually described slightly wrong. Established BLE links do keep meshing after you leave the app. Discovery is what dies: a backgrounded iPhone hides its service UUIDs in Apple's proprietary "overflow area" that non-Apple devices can't decode, so Android can never see it. Realistically the mesh runs while the app is open, with store-and-forward catching you up afterwards.

So it is a possibility in the future, though Knit is currently an Android-first native Kotlin app, not e.g. React Native or similar. So it would mean building an entirely new app on iOS from scratch with feature parity... not necessary a small task :).