Skip to content

Commit 999dc76

Browse files
committed
edits
1 parent 70a8cc2 commit 999dc76

File tree

1 file changed

+22
-20
lines changed

1 file changed

+22
-20
lines changed

articles/communication-services/concepts/ui-library/includes/mobile-ui-use-cases.md

Lines changed: 22 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -8,29 +8,29 @@ ms.date: 09/14/2021
88

99
Use the UI Library for iOS and Android to create calling use cases through the Azure Communication Services call composite. Use composites in Communications Services to easily integrate an entire calling experience in your application by using only a couple lines of code. Composites manage the entire lifecycle of the call, from setup until the call ends.
1010

11-
## Calling use cases
11+
## Call use cases
1212

1313
You can use the call composite in Communication Services to create use cases in these areas:
1414

1515
| Area | Use cases |
1616
| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
1717
| Call types | Join a Microsoft Teams meeting |
1818
| | Join a call by using a group ID |
19-
| [Teams interoperability](../../teams-interop.md) | Call lobby |
20-
| | Transcription and recording alert banner |
21-
| Participant gallery | Remote participants are displayed on a grid |
22-
| | Video preview available throughout call for local user |
23-
| | Default avatars available when video is off |
24-
| | Shared screen content displayed in participant gallery |
25-
| | Participant avatar customization |
26-
| | Participant roster |
27-
| Call configuration | Microphone device management |
28-
| | Camera device management |
29-
| | Speaker device management (wired or Bluetooth) |
30-
| | Local preview available for user to check video |
19+
| [Teams interoperability](../../teams-interop.md) | Join the call lobby |
20+
| | Display a transcription and recording alert banner banner |
21+
| Participant gallery | Show remote participants on a grid |
22+
| | Make video preview available throughout a call for a local user |
23+
| | Make default avatars available when video is off |
24+
| | Show shared screen content in the participant gallery |
25+
| | Enable participant avatar customization |
26+
| | Show the participant roster |
27+
| Call configuration | Manage microphone device |
28+
| | Manage camera device |
29+
| | Manage speaker device (wired or Bluetooth) |
30+
| | Make local preview available for user to check video |
3131
| Call controls | Mute and unmute a call |
32-
| | Video on or off on a call |
33-
| | End call |
32+
| | Turn video on or off during a call |
33+
| | End a call |
3434
| | Hold and resume a call after audio interruption |
3535

3636
## Supported identities
@@ -39,9 +39,11 @@ To initialize a composite and authenticate to the service, a user must have an A
3939

4040
## Teams interoperability
4141

42+
For [Teams interoperability](../../teams-interop.md) scenarios, you can use UI Library composites to join a user to a Teams meeting via Communication Services. To enable Teams interoperability, use the call composite. The composite manages the entire lifecycle of joining a Teams interoperability call.
43+
4244
:::image type="content" source="../../media/mobile-ui/teams-interop-diagram.png" border="false" alt-text="Diagram that shows the Teams interoperability pattern for calling and chat.":::
4345

44-
For [Teams interoperability](../../teams-interop.md) scenarios, you can use UI Library composites to join a user to a Teams meeting via Communication Services. To enable Teams interoperability, use the call composite. The composite manages the entire lifecycle of joining a Teams interoperability call.
46+
The following figure shows an example of the user experience before a caller is added to a Teams meeting:
4547

4648
:::image type="content" source="../../media/mobile-ui/teams-meet.png" alt-text="Screenshot that shows the user experience before a caller is added to a Teams meeting.":::
4749

@@ -77,20 +79,20 @@ Accessibility is a key focus of the calling libraries. You can use a screen read
7779

7880
Use the UI Library for mobile native platforms to give local and remote participants the option to modify how they appear as users in a call. A local participant can choose a local avatar and custom display name when a call begins. A remote user can create a customized avatar when they join the meeting. For more information, see [How to customize participant views](../../../how-tos/ui-library-sdk/data-model.md).
7981

80-
:::image type="content" source="../../media/mobile-ui/ios-composite.gif" alt-text="Gif animation that shows the pre-meeting experience and joining experience on iOS.":::
82+
:::image type="content" source="../../media/mobile-ui/ios-composite.gif" alt-text="GIF animation that shows the pre-meeting experience and joining experience on iOS.":::
8183

8284
## Recommended architecture
8385

8486
Initialize a composite by using an Azure Communication Services access token. It's important to get access tokens from Azure Communication Services through a trusted service that you manage. For more information, see [Quickstart: Create and manage access tokens](../../../quickstarts/access-tokens.md) and the [trusted service tutorial](../../../tutorials/trusted-service-tutorial.md).
8587

86-
:::image type="content" source="../../media/mobile-ui/ui-library-architecture.png" border="false" alt-text="Diagram that shows the recommended architecture.":::
88+
:::image type="content" source="../../media/mobile-ui/ui-library-architecture.png" border="false" alt-text="Diagram that shows the recommended architecture for UI Library.":::
8789

88-
These client libraries also require the context for the call they join. Like user access tokens, disseminate the context to clients by using your own trusted service. The following table summarizes the initialization and resource management functions to operationalize to add context to a client library:
90+
Call and chat client libraries must have the context for the call they join. Like user access tokens, disseminate the context to clients by using your own trusted service. The following table summarizes the initialization and resource management functions that are required to add context to a client library:
8991

9092
| Contoso responsibilities | UI Library responsibilities |
9193
| -------------------------------------------------------- | --------------------------------------------------------------- |
9294
| Provide an access token from Azure | Pass through the provided access token to initialize components |
93-
| Provide a refresh function | Refresh access token by using developer-provided function |
95+
| Provide a refresh function | Refresh the access token by using a developer-provided function |
9496
| Retrieve and pass join information for the call or chat | Pass through call and chat information to initialize components |
9597
| Retrieve and pass user information for any custom data model | Pass through a custom data model to components to render |
9698

0 commit comments

Comments
 (0)