Code Monkey home page Code Monkey logo

100ms-flutter's Introduction

Pub Version Build License Documentation Discord Firebase TestFlight Activity Register

100ms Flutter SDK ๐ŸŽ‰

Prebuilt - Edtech

Integrate Real Time Audio and Video conferencing, Interactive Live Streaming, and Chat in your apps with 100ms Flutter SDK.

With support for HLS and RTMP Live Streaming and Recording, Picture-in-Picture (PiP), CallKit, VoIP, one-to-one Video Call Modes, Audio Rooms, Video Player and much more, add immersive real-time communications to your apps.

Package Version
hms_room_kit Pub Version
hmssdk_flutter Pub Version

๐Ÿ’ป Checkout the 100ms Flutter SDK here

โค๏ธ Checkout the 100ms Prebuilt here

๐Ÿงฑ The Prebuilt QuickStart Guide is available here.

๐Ÿ“– Read the Complete Documentation here: https://www.100ms.live/docs/flutter/v2/guides/quickstart

๐Ÿ“ฒ Download the Sample iOS app here: https://testflight.apple.com/join/Uhzebmut

๐Ÿค– Download the Sample Android app here: https://appdistribution.firebase.dev/i/b623e5310929ab70

100ms Flutter apps are also released on the App Stores, you can download them here:

๐Ÿ“ฒ iOS app on Apple App Store: https://apps.apple.com/app/100ms-live/id1576541989

๐Ÿค– Android app on Google Play Store: https://play.google.com/store/apps/details?id=live.hms.flutter

๐Ÿš‚ Setup Guide

  1. Sign up on https://dashboard.100ms.live/register & visit the Developer tab to access your credentials.

  2. Get familiarized with Tokens & Security here

  3. Complete the steps in Auth Token Quick Start Guide

  4. Get the HMSSDK via pub.dev. Add the hmssdk_flutter to your pubspec.yaml.

๐Ÿ“– Do refer the Complete Installation Guide here.

๐Ÿƒโ™€๏ธ How to run the Example App

The full featured Example app is available here.

๐Ÿš€ We have added explanations & recommended usage guide for different features, UI Layouts, Data Store, etc in Example app ReadMe.

To run the Example App on your system follow these steps -

  1. Clone the 100ms Flutter Github Repo

  2. In project root, run flutter pub get to build the Flutter package

  3. Change directory to example folder

  4. Now, to run the app, simply execute the flutter run command to run the app on a connected device, or iOS simulator, or Android Emulator.

  5. For running on an iOS Device (iPhone or iPad), ensure you have set the Correct Development Team in Xcode Signing & Capabilities section.

The default Example app uses Provider State Management library. For other implementations please check out -

  1. Simple QuickStart
  2. Bloc
  3. Getx
  4. Mobx
  5. Riverpod
  6. Audio Room App
  7. CallKit & VoIP
  8. Flutterflow with Prebuilt
  9. Live Stream with HLS
  10. Full featured App

โ˜๏ธ Minimum Configuration

  • Support for Flutter 3.3.0 or above
  • Support for Android API level 21 or above
  • Support for Java 8 or above
  • Support for iOS 12 or above
  • Xcode 12 or above

๐Ÿค Recommended Configuration

  • Flutter 3.7.0 or above
  • Android API level 33 or above
  • Java 11 or above
  • iOS 16 or above
  • Xcode 14 or above

๐Ÿ“ฑ Supported Devices

  • The Android SDK supports Android API level 21 and above. It is built for armeabi-v7a, arm64-v8a, x86, and x86_64 architectures. Devices running Android OS 12 or above is recommended.

  • iPhone & iPads with iOS version 12 or above are supported. Devices running iOS 16 or above is recommended.

Complete Permissions Guide is available here.

Add the following permissions in the Android's AndroidManifest.xml file -

<uses-feature android:name="android.hardware.camera"/>

<uses-feature android:name="android.hardware.camera.autofocus"/>

<uses-permission android:name="android.permission.CAMERA"/>

<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE"/>

<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS"/>

<uses-permission android:name="android.permission.RECORD_AUDIO"/>

<uses-permission android:name="android.permission.INTERNET"/>

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>

<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />

<uses-permission android:name="android.permission.BLUETOOTH" android:maxSdkVersion="30" />

<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />

๐ŸŽ iOS Permissions

Add following permissions in iOS Info.plist file

<key>NSMicrophoneUsageDescription</key>
<string>{YourAppName} wants to use your microphone</string>

<key>NSCameraUsageDescription</key>
<string>{YourAppName} wants to use your camera</string>

<key>NSLocalNetworkUsageDescription</key>
<string>{YourAppName} App wants to use your local network</string>

๐Ÿง Key Concepts

  • Room A room is the basic object that 100ms SDKs return on successful connection. This contains references to peers, tracks and everything you need to render a live a/v or live streaming app.

  • Peer A peer is the object returned by 100ms SDKs that contains all information about a user - name, role, video track etc.

  • Track A track is a segment of media (audio/video) captured from the peer's camera and microphone. Peers in a session publish local tracks and subscribe to remote tracks from other peers.

  • Role A role defines who can a peer see/hear, the quality at which they publish their video, whether they have permissions to publish video/screenshare, mute someone, change someone's role.

HMSSDK lifecycle

โ™ป๏ธ Setup Update Listeners

100ms SDK provides callbacks to the client app about any change or update happening in the room after a user has joined by implementing HMSUpdateListener. These updates can be used to render the video on the screen or to display other info regarding the room. Let's take a look at the flowchart.

Update Listeners Flowchart

/// 100ms SDK provides callbacks to the client app about any change or update happening in the room after a user has joined by implementing HMSUpdateListener.
/// These updates can be used to render the video on the screen or to display other info regarding the room.
abstract class HMSUpdateListener {


  /// This will be called on a successful JOIN of the room by the user
  ///
  /// This is the point where applications can stop showing their loading state
  /// [room]: the room which was joined
  void onJoin({required HMSRoom room});


  /// This will be called whenever there is an update on an existing peer
  /// or a new peer got added/existing peer is removed.
  ///
  /// This callback can be used to keep a track of all the peers in the room
  /// [peer]: the peer who joined/left or was updated
  /// [update]: the triggered update type. Should be used to perform different UI Actions
  void onPeerUpdate({required HMSPeer peer, required HMSPeerUpdate update});


  /// This is called when there are updates on an existing track
  /// or a new track got added/existing track is removed
  ///
  /// This callback can be used to render the video on screen whenever a track gets added
  ///  [track]: the track which was added, removed or updated
  ///  [trackUpdate]: the triggered update type
  ///  [peer]: the peer for which track was added, removed or updated
  void onTrackUpdate({required HMSTrack track, required HMSTrackUpdate trackUpdate, required HMSPeer peer});


  /// This will be called when there is an error in the system
  /// and SDK has already retried to fix the error
  /// [error]: the error that occurred
  void onHMSError({required HMSException error});


  /// This is called when there is a new broadcast message from any other peer in the room
  ///
  /// This can be used to implement chat is the room
  /// [message]: the received broadcast message
  void onMessage({required HMSMessage message});


  /// This is called every 1 second with a list of active speakers
  ///
  /// ## A HMSSpeaker object contains -
  ///    - peerId: the peer identifier of HMSPeer who is speaking
  ///    - trackId: the track identifier of HMSTrack which is emitting audio
  ///    - audioLevel: a number within range 1-100 indicating the audio volume
  ///
  /// A peer who is not present in the list indicates that the peer is not speaking
  ///
  /// This can be used to highlight currently speaking peers in the room
  /// [speakers] the list of speakers
  void onUpdateSpeakers({required List<HMSSpeaker> updateSpeakers});


  /// This is called when there is a change in any property of the Room
  ///
  ///  [room]: the room which was joined
  ///  [update]: the triggered update type. Should be used to perform different UI Actions
  void onRoomUpdate({required HMSRoom room, required HMSRoomUpdate update});


  /// when network or some other error happens it will be called
  void onReconnecting();


  /// when you are back in the room after reconnection
  void onReconnected();


  /// This is called when someone asks for a change or role
  ///
  /// for eg. admin can ask a peer to become host from guest.
  /// this triggers this call on peer's app
  void onRoleChangeRequest({required HMSRoleChangeRequest roleChangeRequest});


  /// when someone requests for track change of yours be it video or audio this will be triggered
  /// [hmsTrackChangeRequest] request instance consisting of all the required info about track change
  void onChangeTrackStateRequest({required HMSTrackChangeRequest hmsTrackChangeRequest});


  /// when someone kicks you out or when someone ends the room at that time it is triggered
  /// [hmsPeerRemovedFromPeer] it consists of info about who removed you and why.
  void onRemovedFromRoom({required HMSPeerRemovedFromPeer hmsPeerRemovedFromPeer});


  /// whenever a new audio device is plugged in or audio output is changed we
  /// get the onAudioDeviceChanged update
  /// This callback is only fired on Android devices. On iOS, this callback will not be triggered.
  /// - Parameters:
  ///   - currentAudioDevice: Current audio output route
  ///   - availableAudioDevice: List of available audio output devices
  void onAudioDeviceChanged(
      {HMSAudioDevice? currentAudioDevice,
      List<HMSAudioDevice>? availableAudioDevice});


  /// Whenever a user joins a room [onSessionStoreAvailable] is fired to get an instance of [HMSSessionStore]
  /// which can be used to perform session metadata operations
  /// - Parameters:
  ///   - hmsSessionStore: An instance of HMSSessionStore which will be used to call session metadata methods
  void onSessionStoreAvailable(
      {HMSSessionStore? hmsSessionStore});


  /// Upon joining a room with existing peers, onPeerListUpdated will be called with the list of peers present
  /// in the room instead of getting onPeerUpdate for each peer in the room.
  /// Subsequent peer joins/leaves would be notified via both onPeerUpdate and onPeerListUpdated
  void onPeerListUpdate(
      {required List<HMSPeer> addedPeers, required List<HMSPeer> removedPeers});
}

The 100ms SDK sends updates to the application about any change in HMSPeer, HMSTrack, HMSRoom, etc via the callbacks in HMSUpdateListener.

The methods of HMSUpdateListener are invoked to notify updates happening in the room like a peer join/leave, track mute/unmute etc.

More information about Update Listeners is available here.

The following are the different types of updates that are emitted by the SDK -

HMSPeerUpdate
  .peerJoined: A new peer joins the Room
  .peerLeft: An existing peer leaves the Room
  .roleUpdated: When a peer's Role has changed
  .metadataChanged: When a peer's metadata has changed
  .nameChanged: When a peer's name has changed


HMSTrackUpdate
  .trackAdded: A new track (audio or video) is added to the Room
  .trackRemoved: An existing track is removed from the Room
  .trackMuted: A track of a peer is muted
  .trackUnMuted: A muted track of a peer was unmuted
  .trackDegraded: When track is degraded due to bad network conditions
  .trackRestored: When a degraded track is restored when optimal network conditions are available again


HMSRoomUpdate
  .roomMuted: When room is muted to due external interruption like a Phone Call
  .roomUnmuted: When a muted room is unmuted when external interruption has ended
  .serverRecordingStateUpdated: When Server recording state is updated
  .browserRecordingStateUpdated: When Browser recording state is changed
  .rtmpStreamingStateUpdated: When RTMP is started or stopped
  .hlsStreamingStateUpdated: When HLS is started or stopped
  .hlsRecordingStateUpdated: When HLS recording state is updated

๐Ÿ™ Join a Room

To join and interact with others in audio or video call, the user needs to join a room.

To join a Room, your app should have -

  1. User Name - The name which should be displayed to other peers in the room.
  2. Authentication Token - The Client side Authentication Token generated by the Token Service.

To join a room we need an authentication token as mentioned above. There are two methods to get the token:

Fetch token using room-code method (Recommended)

We can get the authentication token using room-code from meeting URL.

Let's understand the subdomain and code from the sample URL In this URL: https://public.app.100ms.live/meeting/xvm-wxwo-gbl

  • Subdomain is public
  • Room code is xvm-wxwo-gbl

Now to get the room-code from meeting URL we can write our own logic or use the getCode method from here

To generate token we will be using getAuthTokenByRoomCode method of HMSSDK. This method has roomCode as a required parameter, userId & endPoint as optional parameter.

This method should be called after calling the build method.

Let's checkout the implementation:

  //This returns an object of Future<dynamic> which can be either
  //of HMSException type or String? type based on whether
  //method execution is completed successfully or not

  dynamic authToken = await hmsSDK.getAuthTokenByRoomCode(roomCode: 'YOUR_ROOM_CODE');

  if(authToken is String){
    HMSConfig roomConfig = HMSConfig(
        authToken: authToken,
        userName: userName,
      );

    hmsSDK.join(config: roomConfig);
  }
  else if(authToken is HMSException){
    // Handle the error
  }

Get temporary token from dashboard

To test audio/video functionality, you need to connect to a 100ms room; please check the following steps for the same:

  1. Navigate to your 100ms dashboard or create an account if you don't have one.
  2. Use the Video Conferencing Starter Kit to create a room with a default template assigned to it to test this app quickly.
  3. Go to the Rooms page in your dashboard, click on the Room Id of the room you created above, and click on the Join Room button on the top right.
  4. In the Join with SDK section you can find the Auth Token for role ; you can click on the 'copy' icon to copy the authentication token.

Token from 100ms dashboard is for testing purposes only, For production applications you must generate tokens on your own server. Refer to the Management Token section in Authentication and Tokens guide for more information.

You can also optionally pass these fields in the HMSSDK constructor -

  1. Track Settings - Such as joining a Room with Muted Audio or Video using the HMSTrackSetting object. More information is available here.

  2. User Metadata - This can be used to pass any additional metadata associated with the user using metadata of HMSConfig object. For Eg: user-id mapping at the application side. More information is available here.

More information about Joining a Room is available here.

// create a class that implements `HMSUpdateListener` and acts as a data source for our UI
class Meeting implements HMSUpdateListener {

    late HMSSDK hmsSDK;

    Meeting() {
        initHMSSDK();
    }

    void initHMSSDK() async {
        hmsSDK = HMSSDK(); // create an instance of `HMSSDK` by invoking it's constructor
        await hmsSDK.build(); // ensure to await while invoking the `build` method
        hmsSDK.addUpdateListener(this); // `this` value corresponds to the instance implementing HMSUpdateListener
        HMSConfig config = HMSConfig(authToken: 'eyJH5c', // client-side token generated from your token service
                                userName: 'John Appleseed');
        hmsSDK.join(config: config); // Now, we are primed to join the room. All you have to do is call `join` by passing the `config` object.
    }

    ... // implement methods of HMSUpdateListener
}

๐ŸŽž Display a Track

It all comes down to this. All the setup so far has been done so that we can show live-streaming videos in our beautiful app.

100ms Flutter Package provides the HMSVideoView widget that renders the video on the screen.

We simply have to pass a Video Track object to the HMSVideoView to begin automatic rendering of Live Video Stream.

We can also optionally pass props like key, scaleType, mirror to customize the HMSVideoView widget.

HMSVideoView(
  track: videoTrack,
  key: Key(videoTrack.trackId),
),

More information about displaying a Video is available here.

๐Ÿ‘‹ Leave Room

Once you're done with the meeting and want to exit, call leave on the HMSSDK instance that you created to join the room.

Before calling leave, remove the HMSUpdateListener instance as:

// updateListener is the instance of class in which HMSUpdateListener is implemented
hmsSDK.removeUpdateListener(updateListener);

To leave the meeting, call the leave method of HMSSDK and pass the hmsActionResultListener parameter to get a success callback from SDK in the onSuccess override method as follow.

You will need to implement the HMSActionResultListener interface in a class to get onSuccess and onException callback. To know about how to implement HMSActionResultListener check the docs here

class Meeting implements HMSActionResultListener{
//this is the instance of class implementing HMSActionResultListener
await hmsSDK.leave(hmsActionResultListener: this);

@override
  void onSuccess(
      {HMSActionResultListenerMethod methodType = HMSActionResultListenerMethod.unknown, Map<String, dynamic>? arguments}) {
        switch (methodType) {
          case HMSActionResultListenerMethod.leave:
          // Room leaved successfully
          // Clear the local room state
          break;
          ...
        }
      }
}

More information about Leaving a Room is available here.

๐Ÿ›ค HMSTracks Explained

HMSTrack is the super-class of all the tracks that are used inside HMSSDK. Its hierarchy looks like this -

HMSTrack
    - AudioTrack
        - LocalAudioTrack
        - RemoteAudioTrack
    - VideoTrack
        - LocalVideoTrack
        - RemoteVideoTrack

๐Ÿ›ค How to know the type and source of Track?

HMSTrack contains a field called source which denotes the source of the Track.

Source can have the following values -

  • regular For normal Audio or Video being published by peers
  • screen For Screenshare track whenver a peer starts Broadcasting their Screen in a Room
  • plugin For a custom Audio or Video plugin being used in Room

To know the type of track, check the value of type which would be one of the enum values - AUDIO or VIDEO

๐Ÿ“จ Chat Messaging

You can send a chat or any other kind of message from a local peer to all remote peers in the room.

To send a message first create an instance of HMSMessage object.

Add the information to be sent in the message property of HMSMessage.

Then use the sendBroadcastMessage function on the instance of HMSSDK for broadcast message, sendGroupMessage for group message and sendDirectMessage for direct message.

When you(the local peer) receives a message from others(any remote peer), void onMessage({required HMSMessage message}) function of HMSUpdateListener is invoked.

More information about Chat Messaging is available here.

// onMessage is HMSUpdateListener method called when a new message is received
@override
void onMessage({required HMSMessage message}) {
  //Here we will receive messages sent by other peers
}


///[message]: Message to be sent
///[type]: Message type(More about this at the end)
///[hmsActionResultListener]: instance of class implementing HMSActionResultListener
//Here this is an instance of class that implements HMSActionResultListener i.e. Meeting
hmsSDK.sendBroadcastMessage(
  message: message,
  type: type,
  hmsActionResultListener: this);


///[message]: Message to be sent
///[peerTo]: Peer to whom message needs to be sent
///[type]: Message type(More about this at the end)
///[hmsActionResultListener]: instance of class implementing HMSActionResultListener
//Here this is an instance of class that implements HMSActionResultListener i.e. Meeting
hmsSDK.sendDirectMessage(
  message: message,
  peerTo: peerTo,
  type: type,
  hmsActionResultListener: this);


///[message]: Message to be sent
///[hmsRolesTo]: Roles to which this message needs to be sent
///[type]: Message type(More about this at the end)
///[hmsActionResultListener]: instance of class implementing HMSActionResultListener
//Here this is an instance of class that implements HMSActionResultListener i.e. Meeting
hmsSDK.sendGroupMessage(
    message: message,
    hmsRolesTo: rolesToSendMessage,
    type: type,
    hmsActionResultListener: this);



@override
void onSuccess(
  {HMSActionResultListenerMethod methodType =
    HMSActionResultListenerMethod.unknown,
    Map<String, dynamic>? arguments}) {

    switch (methodType) {

      case HMSActionResultListenerMethod.sendBroadcastMessage:
      //Broadcast Message sent successfully
      break;

      case HMSActionResultListenerMethod.sendGroupMessage:
      //Group Message sent successfully
      break;

      case HMSActionResultListenerMethod.sendDirectMessage:
      //Direct Message sent successfully
      break;
      ...
    }
  }


@override
void onException(
  {HMSActionResultListenerMethod methodType =
    HMSActionResultListenerMethod.unknown,
    Map<String, dynamic>? arguments,
    required HMSException hmsException}) {

    switch (methodType) {

      case HMSActionResultListenerMethod.sendBroadcastMessage:
      // Check the HMSException object for details about the error
      break;

      case HMSActionResultListenerMethod.sendGroupMessage:
      // Check the HMSException object for details about the error
      break;

      case HMSActionResultListenerMethod.sendDirectMessage:
      // Check the HMSException object for details about the error
      break;
      ...
    }

  }

๐Ÿงฑ The Prebuilt QuickStart Guide is available here.

๐Ÿ“– Do refer the Complete Documentation Guide available here.

๐Ÿƒโ™€๏ธ Checkout the Example app implementation available here.

๐Ÿš€ We have added explanations & recommended usage guide for different features, UI Layouts, Data Store, etc in Example app ReadMe.

100ms Flutter apps are released on the App Stores, you can download them here:

๐Ÿ“ฒ iOS app on Apple App Store: https://apps.apple.com/app/100ms-live/id1576541989

๐Ÿค– Android app on Google Play Store: https://play.google.com/store/apps/details?id=live.hms.flutter

100ms-flutter's People

Contributors

arunshaik2001 avatar arunshaik4321 avatar decoder07 avatar dependabot[bot] avatar govindmaheshwari2 avatar jashan1498 avatar moses12345 avatar mosesatjtc avatar nixon-samuel avatar stanwolverine avatar viveky259259 avatar ygit avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

100ms-flutter's Issues

Add support for Flutter Web

Hi, we are using Flutter web for our WebApp and we need to integrate RTC. 100ms seems very powerful and we would like to give it a try.

At the moment we are not sure if it is supported for "Flutter for Web" or other native desktop platforms like Windows, Linux and macOS.

Let us know if it is supported already or if not, you guys have any plans to support it anytime soon!

Create wrapper class for HMSRoom

@objcMembers public class HMSRoom : NSObject {

    public let id: String

    public let name: String

    public let metaData: String?

    public var peers: [HMSSDK.HMSPeer]
}

Create wrapper class for HMSRole

public struct HMSRole : Codable {

    public let name: String

    public let publishSettings: HMSPublishSettings

    public let subscribeSettings: HMSSubscribeSettings

    public let permissions: HMSPermissions

    public let priority: Int

    public let generalPermissions: [String : String]?

    public let internalPlugins: [String : String]?

    public let externalPlugins: [String : String]?
}

Implement Preview APIs

public func preview(config: HMSConfig, delegate: HMSPreviewListener)

@objc public protocol HMSPreviewListener: AnyObject {
    @objc(onPreview:localTracks:) func onPreview(room: HMSRoom, localTracks: [HMSTrack])
    @objc(onError:) func on(error: HMSError)
}

Cleanup sample app UI & code style

  • UI similar to Android/iOS sample apps
  • Conforming to standard code naming & structure guidelines
  • Use a linter to point warnings & code smells

Create wrapper class for HMSPeer

@objcMembers public class HMSPeer : NSObject {

    public let peerID: String

    public var name: String

    public let isLocal: Bool

    public var role: HMSSDK.HMSRole?

    public let customerUserID: String?

    public var customerDescription: String?

    public var audioTrack: HMSAudioTrack?

    public var videoTrack: HMSVideoTrack?

    public var auxiliaryTracks: [HMSTrack]?
}

Implement Role Change APIs

public func changeRole(for peer:HMSRemotePeer, to role: HMSRole, force: Bool = false) 
    
public func accept(changeRole request: HMSRoleChangeRequest) 

func on(roleChangeRequest: HMSRoleChangeRequest)

public class HMSRoleChangeRequest: NSObject {
    public let suggestedRole: HMSRole
    public let requestedBy: HMSPeer
}

Create wrapper class for HMSConfig

@objcMembers public class HMSConfig : NSObject {

    /// the name that the user wants to be displayed while in the room
    public let userName: String

    public let userID: String

    public let roomID: String

    /// the auth token to be used
    public let authToken: String

    public let shouldSkipPIIEvents: Bool

    /// any json string or metadata that can be passed while joining
    public let metaData: String?

    /// to override the default endpoint (advanced)
    public let endpoint: String?

    public init(userName: String = "iOS User", userID: String, roomID: String, authToken: String, shouldSkipPIIEvents: Bool = false, metaData: String? = nil, endpoint: String? = nil)
}

Create wrapper class for HMSTrack

// HMSTrack

open class HMSTrack : NSObject {

    open var trackId: String { get }

    open var kind: HMSTrack! { get }

    open var source: Int32 { get }

    open var trackDescription: String { get }
    
    open func isMute() -> Bool
}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.