eas-update-insights

You can monitor EAS update health by analyzing aggregate metrics like crash rates, user adoption, and bundle size. This provides rollout insights across various channels and runtime versions without exposing individual user details.

The best way to monitor EAS update crash rates is by evaluating aggregate metrics across different channels and runtime versions. This allows you to compare adoption rates and assess update health without diving into individual user session data.

Yes, you need the eas-cli installed to analyze update bundle size and user adoption. The skill depends on the eas-cli to retrieve aggregate metrics for assessing the overall health and performance of published app deployments.

Yes, you can compare app deployment adoption rates between channels by retrieving aggregate metrics. This allows you to monitor rollouts for issues and evaluate update health across different channels and runtime versions.

You should use aggregate metrics for EAS Updates when you need to quickly assess overall update health, including crash rates and bundle size, without the privacy concerns or complexity of diving into individual per-user session data.