We spent 2 weeks implementing the New Architecture and trying to understand its benefits and limits. That included asking friends at Instagram, Spotify, and other teams what they thought.

It wasn't even close to being ready. And worse: unreliable. We pivoted and spent the winter in "deep work" mode learning Swift..

That moment was a "bet the farm" kind of moment. We knew that AI struggled hard with Swift/SwiftUI and understanding the layout of the applications.

Worse, there are no crypto packages to lean on like viem or @peterferguson.eth's react-native-passkeys.

So we just wrote everything ourselves using Swift Crypto. And got way better at prompting.

Predictions Protocol https://onit.fun | react-native-passkeys maintainer | Variant Founder Fellow | Cambridge Alum | Formerly Ireland's #3 powerlifter (74kg)

That moment was a "bet the farm" kind of moment. We knew that AI struggled hard with Swift/SwiftUI and understanding the layout of the applications.

Worse, there are no crypto packages to lean on like viem or @peterferguson.eth's react-native-passkeys.

So we just wrote everything ourselves using Swift Crypto. And got way better at prompting.

https://github.com/apple/swift-crypto

will you spin out / OS the swift library?

Would love to CTO, but will need funds/grants from EF to cover the roadmap and maintainer workload. Otherwise we have a patchy library that only covers specific use cases.