| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Designing Apps In Meetings | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/design/designing-apps-in-meetings.md | The shared meeting stage is all about collaboration and participation. Here are |-|--| |1|**App icon**: The highlighted icon indicates the app's in-meeting tab is open.| |2|**Share to meeting button**: The entry point to share the app to the meeting. Displays if you configure your app to use the shared meeting stage.|-|3|**Presenter attribution**: Displays the name of the participant who shared the app.| -|4|**iframe**: Displays your app content.| -|5|**Stop sharing button**: Stops sharing the app to the meeting stage. Displays only for the participant who started the share.| +|3|**iframe**: Displays your app content.| +|4|**Stop sharing button**: Stops sharing the app to the meeting stage. Displays only for the participant who started the share.| +|5|**Presenter attribution**: Displays the name of the participant who shared the app.| ### Anatomy: Share specific app content to a meeting The shared meeting stage is all about collaboration and participation. Here are |-|--| |1|**App icon**: The highlighted icon indicates the app's in-meeting tab is open.| |2|**Share to meeting button**: The entry point to share the app to the meeting. For a consistent experience, always use the standard Teams share icon. **Share to meeting** is the recommended default text, but you can also customize it for your use cases. For example, **Play together** for a gaming app or **Watch together** for a video app. Either way, make it clear that the action will create a shared, interactive experience with everyone in the meeting.|-|3|**Presenter attribution**: Displays the name of the participant who shared the app.| -|4|**iframe**: Displays your app content.| -|5|**Stop sharing button**: Stops sharing the app to the meeting stage. Displays only for the participant who started the share.| +|3|**iframe**: Displays your app content.| +|4|**Stop sharing button**: Stops sharing the app to the meeting stage. Displays only for the participant who started the share.| +|5|**Presenter attribution**: Displays the name of the participant who shared the app.| ### Responsive behavior: Shared meeting stage |
| platform | Bots | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/design/bots.md | You can use bots in the following contexts: |1|**App name and icon**| |2|**Chat tab**: Opens the space to talk with your bot (applicable only to personal apps).| |3|**Custom tabs**: Opens other content related to your app.|-|4|**Chat bubble**: Bot conversations use the Teams messaging framework.| -|5|**Adaptive Card**: If your bot's responses include Adaptive Cards, the card takes up the full width of the chat bubble.| +|4|**About tab**: Displays basic information about your app.| +|5|**Chat bubble**: Bot conversations use the Teams messaging framework.| +|6|**Adaptive Card**: If your bot's responses include Adaptive Cards, the card takes up the full width of the chat bubble.| #### Desktop |
| platform | Design Teams Task Modules | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/task-modules/design-teams-task-modules.md | Lists work nicely in a task module because they're easy to scan. #### Desktop ### Form Task modules are a great place to surface forms with sequential user inputs and #### Mobile #### Desktop ### Sign in |