I think our use case is not so especial, as I said our code base almost entirely written in Rust, and building FFI for rust and using tools to even generate the binding for us is really amazing, and easier than write two binding one for java using NDK and the other one for Swift which I guess also would require writing binding too, we going to just to ignoring that there is overhead to serialization/deserialization because channels using json message passing, which is not so bad, but it wouldn't be easy as the FFI approach.
Just Write once deploy everywhere :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think our use case is not so especial, as I said our code base almost entirely written in Rust, and building FFI for rust and using tools to even generate the binding for us is really amazing, and easier than write two binding one for java using NDK and the other one for Swift which I guess also would require writing binding too, we going to just to ignoring that there is overhead to serialization/deserialization because channels using json message passing, which is not so bad, but it wouldn't be easy as the FFI approach.
Just Write once deploy everywhere :)