Building Digital Products
Rust in the Enterprise
Explore ways to engage your CTO, and help engineering leads and enterprise architects to adopt it
The real next-generation in technology adoption
Benefits of Rust in the Enterprise
At Red Badger, we believe in using modern technologies and development patterns to build digital products that meet the unique requirements of blue-chip enterprises. Among these technologies, we see a particular shift towards the Rust programming language as it offers numerous benefits that can radically transform the way enterprises approach digital product development.
Rust is a key tool in building safer, more scalable, more testable, and cost-effective complex, multi-platform applications. With its ability to build delightful digital products on multiple platforms, set engineering teams up for continuous innovation, control build and run costs, secure apps at scale, speed up release cycles, and reduce technical debt, Rust is poised to go viral within the enterprise in 2023.
Originally adopted as a system programming language, we believe that Rust's potential for complex application development is inevitable for enterprises. That's why we have created the Rust Hub, a community of thinkers, builders, and adopters, to advocate and support the adoption of Rust. And, as a pioneer in Rust-based development, we have taken the lead by developing CRUX, a new approach to multi-platform digital products serving iOS, Android, and Web, based on a central Rust business logic core.
Join us in our journey to revolutionise the way enterprises approach digital product development with Rust.
Stuart Harris speaks at February's Rust Nation 23
Introducing...
Headless app
development in RUST
Introducing CRUX
An open-source framework to help you write native User Interface applications for Mobile, Web, Desktop and beyond, faster and with fewer bugs — by sharing your application’s behaviour as a single and easy-to-test Rust core that you can reuse with confidence on every platform.
Most apps need to be built three times – once for iOS (hopefully in Swift), once for Android (hopefully in Kotlin), once for web (hopefully in TypeScript) – with no code reuse, no saving of effort, and no learning from issues. Clearly, there’s no economy in doing the same thing three or more times, and so the industry has been on a years-long hunt for a way of sharing effort and reusing code — a way of building apps just once.
But a good solution to this problem seems to forever elude us. Maybe we’re trying to answer the wrong question...?
We have a number of options that we can use today; React Native (but probably have to think about the Web separately); Kotlin Multiplatform Mobile (KMM), or Flutter (with Dart); Or we can go hybrid and use something like Capacitor with Ionic.
None of these are bad choices, but they all have significant downsides. We think we can do better than that — mostly by deciding which bits are worth sharing and which bits are not.