July 28, 2023

Overview

Highlights include:

  • daily-ios adds support for Adaptive HEVC (H.265 and H.264) streaming via a new iOSOptimized publishing encoding mode.
  • In daily-android, daily-ios, and daily-react, you can now modify a user's admin permissions from within a call using the new canAdmin permission.
  • daily-android and daily-ios both add support for staged subscriptions. Using staged subscriptions, allows your app to remain performant while also being able to increase the participant count. Learn more in our best practices guide.

daily-android

0.9.0

Admin permissions

Admin permissions can now be configured prior to joining a meeting or dynamically from within a meeting. This new permission can be controlled through the updatePermissions method.

Release notes

For more information, check out the release notes.

daily-ios

0.9.0

Adaptive HEVC

Deliver higher quality video using less bandwidth and CPU with Daily's Adaptive HEVC feature, available only on iOS. When enabling the iOSOptimized mode for a call, your daily-ios client will send both a high quality HEVC (also known as H.265) encoded video stream and a medium and low quality H.264 encoded video stream. This setting will ensure your application delivers a high-quality, efficient stream to iOS devices while still remaining cross-platform compatible by sending H.264 streams to other clients.

This feature is available as an updatePublishing encoding mode:

call.updatePublishing(.set( camera: .set( isPublishing: .set(true), sendSettings: .set( maxQuality: .set(.high), encodings: .set(.mode(.iOSOptimized)) ) ) ))

Admin permissions

Admin permissions can now be configured prior to joining a meeting or dynamically from within a meeting. This new permission can be controlled through the updatePermissions method.

Release notes

For more information, check out the release notes.

daily-react

0.11.0

Features

Improvements

  • Improved rendering performance of useParticipantIds and useParticipantProperty: previously both hooks subscribed to all participant objects stored in the recoil state. This led to a lot of unexpected render cycles, e.g. useParticipantIds({ filter: 'remote' }) would re-render when the local participant toggled their cam or mic. We've restructured the way we store and subscribe to changes in participant objects to achieve only targeted re-renders. Every instance of useParticipantIds now sets up its own local state of returned ids, and only updates the state when the resulting array of ids doesn't match the previously stored one. To keep the connection to the recoil state store, we're now using the useRecoilTransactionObserver_UNSTABLE hook which worked flawlessly in our internal tests. Please be aware that with this change we've introduced at least 1 additional render cycle per useParticipantIds to initialize the state.