← Back to context

Comment by ChrisMarshallNY

10 days ago

Looks pretty interesting.

From what I can see, it's a native IOS/MacOS app (SwiftUI). I don't see an Android version.

Also seems pretty spartan, but it looks like it could be embedded in "friendlier" apps.

I find this interesting, there was a briar app that was spoken about a few months ago that was only for android citing that iOS had issues [0] with apps running in background, wonder if/how this was solved here.

Also, I have not seen unlicense before -- guess I'm one of todays lucky 10,000

[0] https://code.briarproject.org/briar/briar/-/wikis/FAQ#will-t...

  • IOS/Apple Bluetooth is an interesting place.

    Backrounding is kinda klunky. I think it's deliberate, as that's a real security vector.

  • Isn't Briar all JVM? AFAIK that can't really run on iOS at all since Apple disallows foreign JITs; unless they compiled Briar to native.

No android but “can” be built?

> protocol is designed to be platform-agnostic. An Android client can be built

https://github.com/jackjackbits/bitchat?tab=readme-ov-file#a...

  • As long as it's Swift, I guess. The Protocols files seem "agnostic." I think the lower-level hardware files might need to be rewritten, though, so he's saying that an Android developer could write an app that incorporates the protocol.

    If I were an Android developer, though, I'd just use the Swift files as a requirements spec, and write it native.

>Universal App

For Apple only. In what way is this universal?

  • It is Apple terminology for an app that supports both iPad and iPhone.

    • And Mac.

      SwiftUI apps can often do both.

      I’m probably gonna rewrite my Bluetooth explorer app in SwiftUI. Doesn’t need any fancy UI.

  • Hey, could be worse. A universal Windows Mobile 10 app wouldn't run on Windows Phone 8 even though WP8 had many more installed devices than WM10.