:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
chore(mobile): accept simulator and emulator screenshots for ui changes (#128446)
Chris Volzerfdf0defd2430
diff --git a/products/mobile/AGENTS.md b/products/mobile/AGENTS.mdindex 956c2c9e1da3..e746946882a6 100644--- a/products/mobile/AGENTS.md+++ b/products/mobile/AGENTS.md@@ -10,7 +10,8 @@ The app is its own pnpm workspace. Run every command from `products/mobile`.## Pull request screenshots-Every PR touching `products/mobile/` must include before-and-after screenshots from **both a physical iOS device and a physical Android device** if it changes frontend or user-facing behavior.+Every PR touching `products/mobile/` must include before-and-after screenshots from **both iOS and Android** if it changes frontend or user-facing behavior.+An iOS simulator or an Android emulator qualifies for its platform, as does a physical device.This includes layout, styling, copy, navigation, interactions, and loading, empty, or error states.Capture both platforms even when the intended change is platform-specific, so reviewers can check the other platform for regressions.PRs with no frontend or user-facing impact should explain why screenshots do not apply.@@ -19,14 +20,13 @@ PRs with no frontend or user-facing impact should explain why screenshots do not2. Run the proposed revision on the same devices and capture the same screens and states, with matching data and orientation.For a new screen, capture the existing entry point or flow as the before state.3. Attach the screenshot pairs to the PR description, labeled **iOS before**, **iOS after**, **Android before**, and **Android after**.- Record each device's model, OS version, and screen size alongside its screenshots.+ Record the model, OS version, screen size, and whether each capture used a physical device, simulator, or emulator.4. Prefer repeating the comparison on multiple screen sizes per platform, including smaller and larger phones where available.Record the sizes tested so reviewers can see the coverage.-Use device screenshots or available device tooling, such as Argent or Device Hub, with the physical device selected explicitly.-Simulator, emulator, and web screenshots are useful during development but do not satisfy the physical-device requirement.+Capture the native app on the selected device, simulator, or emulator. Web previews can supplement the native screenshots.A recording may supplement the screenshot pairs to show an interaction.Before uploading screenshots, read the [repository PR guidance](../../AGENTS.md#pr-descriptions) for public asset requirements.Use demo or invented data.-If a physical device or either platform's screenshots are unavailable, state the missing coverage in the PR and arrange device testing before marking it ready for review.+If either platform's screenshots are unavailable, state the missing coverage in the PR and arrange device testing before marking it ready for review.