And once the data processing code was in Rust, it made sense to have the endpoint that collected the data in Rust too. It would probably have been possible to optimise the node/python versions. But it was easier to write it in Rust that is designed for these high-performance scenarios.
An unexpected bonus was just how reliable our Rust code turned out to be. I'd definitely consider Rust for non-performance critical code on that basis.
(but then again who cares when you can just piggyback off Electron)
Rust doesn't do so well in the mobile app space.
Still, a very large portion of mobile apps are connecting to some back end service. I think I have exactly one app that stores it's data locally without a server connection (not counting games).
Additionally really don't see a need for having to deal with the borrow checker in distributed computing applications, instead of tracing GC + value types.
Rust's ideal place is like where Oracle, Apple, Google and Microsoft are placing C++, OS low level libraries, audio codecs, graphics drivers.