chore(insights): Update docs for new Mobile Vitals insights module (#12366)

* chore(insights): Update docs for upcoming mobile screens GA

* Update links and redirects

* Add screenshot for mobile-screens, add frames delay section

* Update docs/product/insights/mobile/mobile-screens/screen-loads.mdx

Co-authored-by: Karl Heinz Struggl <[email protected]>

* Apply suggestions from code review

Co-authored-by: Alex Krawiec <[email protected]>

* Update index.mdx

* Rename Mobile Screens to Mobile Vitals

* Fix CI errors

* Refine docs based on feedback

* Address PR feedback

---------

Co-authored-by: Karl Heinz Struggl <[email protected]>
Co-authored-by: Alex Krawiec <[email protected]>

Author: 3 people

docs/concepts/search/searchable-properties/events.mdx

@@ -342,13 +342,13 @@ Returns results with a matching maximum value for the field entered.
 
 ### `measurements.app_start_cold`
 
-A [cold start](/product/insights/mobile-vitals/#app-start) refers to when the app launches for the first time after a reboot or update. The app is not in memory and no process exists.
+A [cold start](/product/insights/mobile/mobile-vitals/app-starts/) refers to when the app launches for the first time after a reboot or update. The app is not in memory and no process exists.
 
 - **Type:** duration
 
 ### `measurements.app_start_warm`
 
-A [warm start](/product/insights/mobile-vitals/#app-start) refers to when the app has already launched at least once and is partially in memory. For instance, the user backs out of your app, but then re-launches it. The process may have continued to run, but the app must recreate the activity from scratch.
+A [warm start](/product/insights/mobile/mobile-vitals/app-starts/) refers to when the app has already launched at least once and is partially in memory. For instance, the user backs out of your app, but then re-launches it. The process may have continued to run, but the app must recreate the activity from scratch.
 
 - **Type:** duration
 
@@ -378,7 +378,7 @@ A [warm start](/product/insights/mobile-vitals/#app-start) refers to when the ap
 
 ### `measurements.frames_frozen`
 
-[Slow and frozen frames](/product/insights/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
+[Slow and frozen frames](/product/insights/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
 
 - **Type:** number
 
@@ -390,7 +390,7 @@ Returns results with a matching rate of frozen frames. That is, `measurements.fr
 
 ### `measurements.frames_slow`
 
-[Slow and frozen frames](/product/insights/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
+[Slow and frozen frames](/product/insights/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
 
 - **Type:** number
 

docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx

@@ -147,7 +147,7 @@ You can opt out of Activity Instrumentation and App Start Instrumentation using
 </application>
 ```
 
-Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile-vitals).
+Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals).
 
 ### Slow and Frozen Frames
 
@@ -159,7 +159,7 @@ Supported on Android OS version `7.0` and above.
 
 Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are _slow frames_ and _frozen frames_. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the [Activity](/platforms/android/tracing/instrumentation/automatic-instrumentation/#activity-instrumentation) transactions.
 
-Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile-vitals).
+Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals).
 
 ### Trace Propagation Targets
 

docs/platforms/android/tracing/instrumentation/perf-v2.mdx

@@ -11,7 +11,7 @@ Supported in Sentry's Android SDK version `7.4.0` and above.
 
 </Alert>
 
-Performance V2 is a set of features which enrich your existing instrumentation, giving you more insights into potential performance bottlenecks. These features tightly integrate with [Mobile Vitals](/product/insights/mobile-vitals/).
+Performance V2 is a set of features which enrich your existing instrumentation, giving you more insights into potential performance bottlenecks. These features tightly integrate with the [Mobile Vitals](/product/insights/mobile/mobile-vitals/) insights module.
 
 ### Enabling Performance V2
 

docs/platforms/apple/common/features/index.mdx

@@ -38,7 +38,7 @@ The SDK builds a crash report that persists to disk. While it attempts to send t
   - Rendering of UIViewControllers
   - Performance of HTTP requests
   - Distributed tracing
-  - <Link to="/product/insights/mobile-vitals">Mobile Vitals</Link>
+  - <Link to="/product/insights/mobile/mobile-vitals">Insights for Mobile Vitals</Link>
     - Cold and warm start
     - Slow and frozen frames
     - <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/#prewarmed-app-start-tracing">Prewarmed App Start Tracing</PlatformLink>

docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx

@@ -123,7 +123,7 @@ Before [sentry-cocoa 8.18.0](https://github.com/getsentry/sentry-cocoa/releases/
 - **UIKit and Application Init**: from pre main initializers to [`didFinishLaunchingNotification`][didfinishlaunching].
 - **Initial Frame Render**: from the [`didFinishLaunchingNotification`][didfinishlaunching] to [`UIWindowDidBecomeVisibleNotification`][uiwindow].
 
-Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile-vitals).
+Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals).
 
 ### Prewarmed App Start Tracing
 
@@ -170,7 +170,7 @@ The detail view of the transaction displays the slow, frozen, and total frames:
 
 ![Slow and Frozen Frames](./img/slow-frozen-frames.png)
 
-Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile-vitals).
+Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals).
 
 ## Network Tracking
 

docs/platforms/flutter/tracing/instrumentation/automatic-instrumentation.mdx

@@ -45,7 +45,7 @@ Learn more in our [App Start Instrumentation](/platforms/flutter/integrations/ap
 
 Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are slow frames and frozen frames. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the transactions you capture.
 
-Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile-vitals).
+Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals).
 
 Learn more how to set it up in our [Slow and Frozen Frames Instrumentation](/platforms/flutter/integrations/slow-and-frozen-frames-instrumentation/) docs.
 

docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx

@@ -53,13 +53,13 @@ If you don't [wrap your root component with Sentry](#wrap-your-root-component),
 
 The SDK differentiates between a cold and a warm start, but doesn't track hot starts or resumes. The measurements are available under `measurements.app_start_warm` and `measurements.app_start_cold`.
 
-Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile-vitals).
+Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals).
 
 ### Slow and Frozen Frames
 
 Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are slow frames and frozen frames. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the transactions you capture.
 
-Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile-vitals).
+Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals).
 
 <Alert>
 

docs/platforms/react-native/tracing/instrumentation/time-to-display.mdx

@@ -6,7 +6,7 @@ sdk: sentry.javascript.react-native
 description: "Learn how to measure time to display with the Sentry React Native SDK."
 ---
 
-Sentry's React Native SDK package ships with a tracing feature that allows you to measure your application's [Time to Display](/product/insights/mobile-vitals/#time-to-initial-display-and-time-to-full-display). This guide will show you how to use Sentry's React Native SDK to measure Time to Display in your application.
+Sentry's React Native SDK package ships with a tracing feature that allows you to measure your application's [Time to Display](/product/insights/mobile/mobile-vitals/#time-to-initial-display-and-time-to-full-display). This guide will show you how to use Sentry's React Native SDK to measure Time to Display in your application.
 
 Time to Display consists of two parts, Time To Initial Display (TTID) and Time To Full Display (TTFD). TTID measures the time it takes to display the first frame, while TTFD measures the time it takes to display the full content for the user to interact with.
 

docs/product/explore/profiling/mobile-app-profiling/metrics.mdx

@@ -16,7 +16,7 @@ The amount of heap memory used by the application is recorded every 100 ms using
 
 ## GPU Information
 
-In addition to counting the number of [slow and frozen UI frame renders](/product/insights/mobile-vitals/#slow-and-frozen-frames) for Mobile Vitals, Sentry now records the timestamp for every frame and overlays it on top of profiling flame charts:
+In addition to counting the number of [slow and frozen UI frame renders](/product/insights/mobile/mobile-vitals/#slow-and-frozen-frames) for Mobile Vitals Insights, Sentry now records the timestamp for every frame and overlays it on top of profiling flame charts:
 
 ![Sentry displays slow and frozen frames above the flamechart of a particular profile.](./img/flamechart-with-gpu-overlay.png)