How about offering Android jni as standard? #161
Replies: 4 comments 3 replies
-
Thanks for the feedback :D It would be great to provide support for more users out there, but may I ask you what do you exactly mean by 'Android API'(Probably Java API) and 'A seperate adapter'? It's kind of hard for me to guess which situation you are in where you had to bypass cargokit. May I take a look at your 'separate adapter' code, if possible? |
Beta Was this translation helpful? Give feedback.
-
The example link I'm trying to implement is here. And the java file you see here will make it look like the following link. Thank you very much for considering my opinion :) |
Beta Was this translation helpful? Give feedback.
-
This idea looks interesting :) However, it seems to go out of the scope of this framework. The main questions is as follows: If we support JNI for Android, why not Objective-C interface for iOS, C interface for Windows, etc? It would make this project support various languages other than Rust, which would be a LOT of work 😅. I can come up with 2 alternative solutions:
|
Beta Was this translation helpful? Give feedback.
-
I thought I could do most of the rust in the project you made! Flutter is a cross-platform, so most of them are supported. If you say you're applying, I'm going to participate in the work. Thank you for listening to me. |
Beta Was this translation helpful? Give feedback.
-
It's great and great to be able to use rust right away.
But when I tried to use Android api, I also had to make a separate adapter using cargokit.
In my opinion, I would like to offer work suggestions for people who will be in the same situation as me.
I'd appreciate your opinion. Thank you :)
Beta Was this translation helpful? Give feedback.
All reactions