NFHTTP VS crux

This is your friendly reminder that Spotify went out of their way to write a networking library that wraps platform specific network libraries since iOS will have special-ish behaviors that you lose if you aren’t using their stack.

I am the biggest proponent of Rust where possible but I always feel like this is worth mentioning when people bring up moving all shared logic for mobile platforms to Rust. It would be great to see it reqwest/ureq/etc could have a feature flag to use these behind the scenes:

https://github.com/nativeformat/NFHTTP

Also: if anybody from Spotify is reading I would love to know why it’s discontinued and passed to community maintenance. Alternatively, if someone from e.g Apple would weigh in on how much this still matters it would also be welcome.

It _has_ been figured out, it's just not something anyone's done in Rust yet: https://github.com/nativeformat/NFHTTP

Found a client library: https://github.com/spotify/NFHTTP

Spotify indeed goes out of their way to use the native handlers, so... there's some prior art.

Another (also Rust-based) cross-platform mobile app dev kit is crux [1]. I've never used it, but the core idea of "true native UIs with a shared business logic core via IPC" seems like the sweet spot to my mostly untrained sensibilities.

[1] https://redbadger.github.io/crux/

Jason - great work here. Your Swift code looks like mine :) on this, some folks in the UK have created Crux - an interesting abstraction layer for mobile apps using Rust. Might provide some ideas for optimisation/ipc. https://github.com/redbadger/crux

Recently, I stumbled upon a project at the Rust London conference that caught my eye. It's called Crux, and it's a library that helps you implement a functional core and imperative shell paradigm. In other words, it allows you to separate your app logic from your UI code, and share it between platforms.