🤔 Does This Project Support @JavascriptInterface-like Annotations for JS-Native Communication?

[strange-qwq]

I noticed the documentation mentions JS-Native interaction only through window.kmpJsBridge.callNative. While the JsBridge name is configurable, it appears restricted to using the callNative method pattern.

In Android projects, we use @JavascriptInterface annotations to expose native methods directly to JS. ​​Does this project support similar annotation-driven approaches?​​

Though JS function mapping could be a workaround, ​​is there a zero-configuration solution that preserves existing frontend code?​​ I'm looking for a way to achieve bidirectional communication without rewriting existing JS invocation logic.

[guyaumetremblay]

@KevinnZou You talk about a customization of the method name here: #80 (reply in thread)

Is it still planned ?