For one of my current clients, we decided to use Rust as our main programming language. There were several reasons behind this decision;
apart from the technical merits, there's also the undisputable fact that Rust is still a relatively new language, fancy and hip –
and when you're a startup, using any technology that came out in the previous decade is just setting yourself up to fail.
I mean, it's logical – how can you innovate without using innovative tech? The fastest way to success is aboard the hype train.
As one of the product's selling point was supposed to be "you own your data", it couldn't be a purely browser-accessible service,
but rather something we'd distribute to the users to run on their own devices. We already had some headless instances running internally,
and with a trivial amount of work, were able to make redistributable packages for Windows and Linux. But we knew that being desktop-only
would be a serious blocker against adoption – if we wanted this to take off, we'd need mobile versions of the app.
This meant we had to figure out how to get our stuff running on Android and, later, on iOS. Seeing how I already had some experience
with cross-compiling and build automation, I volunteered to delve into the topic.