directly calling the iOS sdk?

[bsutton]

It's it possible to call directly into the iOS native SDK without writing objective C bridging code?

I maintain the sounds package and would like to remove all of the objective C code and replace it with pure dart
.
https://pub.dev/packages/sounds

Is this feasible or will I still need to build a bridging layer to call into the iOS SDK?

The SDK API I'm using also uses call backs, are callbacks support by dart native?

[yulingtianxia]

Q: It's it possible to call directly into the iOS native SDK without writing objective C bridging code?
A: Yes.

Q: Is this feasible or will I still need to build a bridging layer to call into the iOS SDK?
A: Just write dart code. DartNative will act as a bridging layer.

Q: The SDK API I'm using also uses call backs, are callbacks support by dart native?
A: Sync/Async callback is supported by DartNative(Only in iOS, callback for Android is under developing)

[bsutton]

OK, I'm excited. Looks like my evening is now mapped out.

…

On Thu, 15 Oct 2020 at 14:19, 杨萧玉 ***@***.***> wrote: Q: It's it possible to call directly into the iOS native SDK without writing objective C bridging code? A: Yes. Q: Is this feasible or will I still need to build a bridging layer to call into the iOS SDK? A: Just write dart code. DartNative will act as a bridging layer. Q: The SDK API I'm using also uses call backs, are callbacks support by dart native? A: Sync/Async callback is supported by DartNative(Only in iOS, callback for Android is under developing) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#30 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG32OCM7P2SRAS5Q7NHCR3SKZS4ZANCNFSM4SRAQRSA> .