|Service||Microsoft Docs article||Related commit history on GitHub||Change details|
|platform||App Fundamentals Overview||https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/app-fundamentals-overview.md||
Teams as a platform offers you toolkits, libraries, and apps at every stage of aUnderstanding the user and their concern are the first indicators of how a Teams app can help. Build your use case around the problem, determine how an app can solve it, and draw a solution.
-* **Understand your use case and Teams App Features**: Understand your user's requirement and you can identify the right features.
+* **Understand your use case and Teams app features**: Understand your user's requirement and you can identify the right features.* **Map your use cases**: Map common use cases to Teams features based on requirements, such as sharing, collaborating, workflows, relevant social platforms, and more.
Microsoft Teams Connect shared channels allow members of a channel to collaborat* Individuals within the same organization. * Individuals and other teams of other organizations.
+> Tab apps in shared channels are available in [Government Community Cloud (GCC), GCC-High, and Department of Defense (DOD)](~/concepts/app-fundamentals-overview.md#government-community-cloud) environments.+ Teams Connect shared channels facilitate secure collaboration seamlessly. Allow external users outside of your organization to collaborate with internal users in Teams without changing their user context. Enhance user experience unlike using guest accounts, for example, the members must sign out of Teams and sign in again using a guest account. Teams applications extend the powerful collaboration space. :::image type="content" source="~/assets/images/app-fundamentals/shared-channels-teams.png" alt-text="Diagram that shows Team B from organization A and Team C from organization B collaborating in a shared Channel as Team A." border="true" :::
|platform||Plan Code Instrumentation||https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/design/plan-code-instrumentation.md||
Azure Applications Insights does auto-instrumentation to automatically collect p- The [retention workbook](/azure/azure-monitor/app/usage-retention) provides user retention analysis out of box. The workbook allows measuring retention by pre-defined custom events. - [User Flows](/azure/azure-monitor/app/usage-flows) provides useful insight on how your users navigate through the app and can be used for tracking custom events as well.
-## Telemetry as an Investment
+## Telemetry as an investmentCollecting instrumentation data using the generated analytics is important for improving your app experience and guiding your roadmap. However, your investment in planning analytics and using instrumentation goes beyond the solution. It provides a window into your userΓÇÖs mind and collects behavior patterns that can help you find the crucial product market fit.
|platform||Plan Responsive Tabs For Teams Mobile||https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md||
After you've identified the app scope, it's time to understand the following thrView apps on mobile. To build an app on mobile, you can start with the consumption experience. Since the mobile world has made scrolling for content a common practice, you can show relevant information. Use engagement mechanisms, such as notifications to inform updates.
-2. **Quick Actions**
+2. **Quick actions**Use app on mobile. After your users start consuming the content on mobile, you can scale your app to the next level by migrating some actions from desktop app. You can optimize and build new actions for mobile.
In the first stage, you can consider desktop experience to show the content and:::image type="content" source="../../assets/images/app-fundamentals/coauthoring-and-whiteboarding-apps-consumption.png" alt-text="Shows content and assets in desktop experience.":::
+Quick actions:In the second stage, you can introduce the following actions:
Engagement intends to measure the intensity and depth of interaction between the| ΓÇó % of users using key features in Teams app vs. using the same feature in a web or native app. | ΓÇó Indicates discoverability, ease of use, and value of using the feature within Teams app. <br> ΓÇó Report at app feature level. | | ΓÇó #, % users using the app across different scopes (R28). | ΓÇó Engagement penetration. <br> ΓÇó Report by scope. <br> ΓÇó Ability to drill down by capability. | | ΓÇó #, % users using the app in different platform capabilities (R28). <br> ΓÇó #, % Interacting with tab. <br> ΓÇó #, % Interacting with Messaging extension. <br> ΓÇó #, % Interacting with bot. <br> ΓÇó #, % Interacting with side panel in a meeting. <br> ΓÇó #, % Interacting with Stage view. | ΓÇó Engagement and value prop of app capabilities. <br> ΓÇó If usage of any of platform capabilities is low, consider drilling into details on ease of use and value add. |
-| **Task Success** | |
+| **Task success** | || ΓÇó % of users completing core action. | ΓÇó Ease of performing core task. <br> ΓÇó Report at a week level. | | ΓÇó User journey in a Teams app ΓÇô Funnel view with user drop offs. | ΓÇó Friction points in user journey. <br> ΓÇó Drill down at a tenant level. | | ΓÇó Lostness Score for core action: <br> :::image type="content" source="../../assets/images/app-fundamentals/lostness-score-core-action.png" alt-text="Lostness score for core action" border="false"::: <br> where, <br> **L** = Lostness <br> **N** = The number of different and unique steps performed while performing core action. <br> **S** = The total number of steps performed while performing core action including repeat steps. <br> **R** = The minimum number of steps required to complete core action. | ΓÇó Ease of use with regional drill provides insights on need for locale. <br> ΓÇó Drill down at region and tenant level. <br> ΓÇó If lostness is above 0.4 then app should improve the user experience to make completing core action easier for users. |
From designing to building and distributing a Teams app, you can use various too1. Extend functionality by adding more Teams capabilities and M365 data with :::image type="icon" source="assets/icons/microsoft-icon.png"::: Microsoft Graph. 1. Test the app on a developer tenant with sample user data. 1. Deploy the app to Azure.
-1. Manage and publish the apps to Store with Developer Portal. Monetize your app with options, such as SaaS offers, in-app purchases, and more.
+1. Manage and publish the apps to Teams store with Developer Portal. Monetize your app with options, such as SaaS offers, in-app purchases, and more.## Next step
Let's look at some areas where an app helps to meet a business need.:::image type="content" source="../msteams-platform/assets/images/overview/why-teams-apps.png" alt-text="Why should you build Teams apps?":::
-| **Development Options** | **Business Opportunities** |
+| **Development options** | **Business opportunities** || | |
-| - Desktop app <br> - Web app <br> - Mobile app | - Increase user engagements <br> - Make your app discoverable on Teams Store |
+| - Desktop app <br> - Web app <br> - Mobile app | - Increase user engagements <br> - Make your app discoverable on Teams store || **Customer benefits** | **Internal workflows** | | - On-the-go accessibility <br> - Secure customer data <br> - Ease of communication | - Automate repetitive tasks <br> - Simplify tasks with bots, <br> such as Q&A and Help-desk |
Here's why Teams is best-suited for your app needs::::image type="content" source="../msteams-platform/assets/images/overview/teams-apps-bot.png" alt-text="Teams app for internal use"::: -- **Teams Store advantage**
+- **Teams store advantage**
- Push your app on Teams store to improve app's availability and you can use it as a marketing opportunity. If you're running a startup, Teams platform helps to increase awareness of your products. Teams Store marketplace can be a great platform for large audiences to discover your app.
+ Push your app on Teams store to improve app's availability and you can use it as a marketing opportunity. If you're running a startup, Teams platform helps to increase awareness of your products. Teams store marketplace can be a great platform for large audiences to discover your app.- **Surface existing app**
|platform||Bots With Tabs||https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/bot-v3/bots-with-tabs.md||
There are two ways of achieving this scenario:2. If you wish to only notify the recipient or interested parties involved with the action, your bot can send a personal chat message to the user. You should first check to see if a personal conversation between your bot and the user exists. If not, you can call `CreateConversation` to initiate the personal chat. In both cases, use event notifications wisely and never spam the user with unnecessary updates.+
+## See also+
+* [Add capabilities to Microsoft Teams app](../../toolkit/add-capability.md)
|platform||Tab Sso Overview||https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/authentication/tab-sso-overview.md||
Here's what your app users get with SSO experience:- The access token is pre-fetched by Teams to improve performance and load time of the app in the Teams environment. - The app users don't need to memorize or record several passwords to access and use apps in Teams environment.
-> App users can't give permission to some permission scopes, such as `Sites.ReadWrite.All`, which allows the app user to read and write to all SharePoint and OneDrive assets in the tenant. For such scopes, only the tenant administrator can grant consent on an app user's behalf.- Now, let's see what happens at the backend during runtime to achieve SSO experience within Teams. ## SSO in Teams at runtime
The following table shows the changes that you can see in the files of your app* [Authenticate users in Microsoft Teams](../concepts/authentication/authentication.md) * [Provision cloud resources](provision.md) * [Create new Teams project](create-new-project.md)
+* [Combine bots with tabs](../resources/bot-v3/bots-with-tabs.md)
Discover Microsoft Teams platform features that are generally available (GA). YoTeams platform features that are available to all app developers.
-* ***March 23, 2023***: [Apps are available for scheduled public channel meetings](apps-in-teams-meetings/teams-apps-in-meetings.md)
-* ***March 20, 2023***: [Bots are available in DOD](bots/what-are-bots.md)
-* ***March 20, 2023***: [Message extensions are available in DOD](messaging-extensions/what-are-messaging-extensions.md)
+* ***April 4, 2023***: [Tab apps in shared channels are available in DOD](~/concepts/build-and-test/shared-channels.md):::column-end::: :::row-end:::
Teams platform features that are available to all app developers.| **Date** | **Update** | **Find here** | | -- | | -|
+| 23/03/2023 | Apps are available for scheduled public channel meetings | Build apps for Teams meetings and calls > [Overview](apps-in-teams-meetings/teams-apps-in-meetings.md) |
+| 20/03/2023 | Bots are available in DOD | Build bots > [Overview](bots/what-are-bots.md)|
+| 20/03/2023 | Message extensions are available in DOD | Build message extensions > [Overview](messaging-extensions/what-are-messaging-extensions.md)|| 28/02/2023 | Facilitate adoption of your app and create awareness | Distribute your app > adoption > [Drive customer adoption of your app](promote-app-adoption.md) | | 27/02/2023 | Changelog for Developer Portal | Tools and SDKs > Developer Portal for Teams > [Overview](concepts/build-and-test/teams-developer-portal.md#changelog-for-developer-portal) | | 23/02/2023 | SSO authentication for your Adaptive Cards Universal Actions | Add authentication > Enable SSO for your Teams app > Enable SSO for Adaptive Cards Universal Actions in your bot > [Overview](task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/enable-sso-for-your-adaptive-cards-universal-action.md) |