Flutter plugins are a great way to run native code from a Flutter app, but they are configured differently than if the native code were to be written directly within Flutter apps. See the template here - it shows what the iOS module for a plugin looks like
I should mention that this plugin will not be published publicly - it is being developed internally (by me) at my company; we have a trial license and are working on obtaining a full one.
I will also add that I’ve successfully configured the Android SDK with this plugin and it works very well.
I know you guys may not know much about Flutter, but I wanted to ask my questions here first before go to other resources.
Here are the technical questions I have for now:
- Do the Zoom libraries (MobileRTC.framework and MobileRTCResources.bundle) only need to be imported into the plugin target (which would be whatever the creator has named the plugin), or do they need to be imported to the Pods-Runner target, and perhaps the Flutter target as well? I doubt it, but I’m not totally clear on this.
- Does the iOS SDK handle launching the Meeting UI when calling
meetingService.joinMeeting()without developers needing to declare any UI related code, like a View or something? For Android I know it does that, but I’m less familiar with iOS coding, and since Flutter iOS plugins don’t build any UI out of the box (it can be done, but differently - see here), the manner of setting up the code is throwing me off a little bit; since the code in the documentation deals with declaring a
UIWindow, and the class extends
UIApplicationDelegate, I’m not clear on this.
- Also, since Flutter iOS plugins do not have an
extension AppDelegate: MobileRTCAuthDelegateisn’t applicable. Would replacing it with the plugin’s class name work instead?
I hope you’ll be able to help provide some insight on this.