[DOCS-14104] Add mobile frustration signals documentation#36263
Open
[DOCS-14104] Add mobile frustration signals documentation#36263
Conversation
github-actions
Bot
added
Architecture
Contributor
Contributor
|
Opened DOCS-14174 to assign a Docs writer and follow up with editorial review. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Fixes DOCS-14104
Adds documentation to reflect existing support for mobile RUM frustration signals (rage taps and error taps) on Android, iOS, Flutter, React Native, and Kotlin Multiplatform. This PR adds dedicated pages for each platform and updates each platform landing page to include frustration signals in the navigation.
Merge instructions
Merge readiness:
Additional notes