React Native got me here. Rust is where I’m going.

React Native is great when you just want to get something out the door without arguing with two separate platform SDKs. It got the job done. It exists. It works. For now, I'm okay with that.

But every time I watch a JavaScript engine deserialize JSON across a bridge just to update a few numbers on screen, a little part of my soul quietly leaves my body. We have gigahertz processors in our pockets, yet we still manage to make basic apps feel like they're wading through cold molasses.

The common advice is always: 'Just optimize your re-renders' or 'Wait for the new architecture.' At some point, you realize you're spending more engineering effort fighting the framework's abstractions than actually building your product. Between random Metro bundler tantrums, bloated dependency trees, and mystery garbage collection pauses, cross-platform JS starts feeling like debt you took out at high interest.

That's why the endgame is Rust. Not because it’s trendy, but because deterministic memory, zero-cost abstractions, and fearless concurrency are genuinely unmatched. When you write a core engine in Rust, you write it once, compile it straight to native machine code, and it runs anywhere without dragging a whole browser runtime along for the ride.

The plan isn't to burn everything down overnight. Ship first, validate the product, and keep things moving. But the next iteration won't be another layer of React Native duct tape. It'll be a lean, unapologetic Rust core with tiny native shells on top. Fast, tiny, and built to outlive the next ten frontend framework hypecycles.