C ABI or minimal FFI-friendly ABI

[canadaduane]

From praveen6747:

Is there a stable C ABI or minimal FFI-friendly interface exposed from the Rust core that would allow integration via Flutter FFI?
Are there any examples or guidance for using Loro in mobile environments (iOS/Android)?
Is the sync protocol documented well enough to implement a custom transport layer (e.g., WebSocket-based sync)?

From your perspective, what would be the recommended approach for integrating Loro into a cross-platform mobile app?
Context
I require true cross-platform support.
Offline-first behavior is important.
The app may expand beyond chat into collaborative features later.
I am trying to avoid building a heavy backend if peer-to-peer or lightweight sync is feasible.
I would appreciate any architectural suggestions, warnings, or best practices before I commit deeply to this direction.
Thank you again for your work — it’s very promising.

I think you're kind of asking two questions, let me see if that's right:

• how to use loro-extended in Flutter
• how to communicate with other loro-extended nodes, from Flutter

While Loro itself is built in Rust and has a library (see https://crates.io/crates/loro, https://crates.io/crates/loro-ffi), LoroExtended is typescript-only. So there are a few layers here that you would need to figure out to make it compatible with Flutter--your instinct around an FFI for Loro itself is correct, as that would be the first hurdle.

A lighter-weight step is to just communicate with a LoroExtended Repo of docs. The websocket adapter has a CBOR protocol that you could use to communicate, see https://github.com/SchoolAI/loro-extended/blob/main/adapters/websocket/PROTOCOL.md

I've actually used this protocol in a standalone Rust instance to talk to a LoroExtended Repo without having to implement the full "document repo" code. In my case, I was adapting the Zed editor (which already has its own CRDT for text) to communicate with LoroExtended. So that may not be as useful to you.