You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Session replay: record/ignore screens via remote config #558
Today recording starts and ends automatically.
We need to give the option to either choose which screens have to be recorded/ignored, or the ability to start/pause dynamically as well.
But that's only the imperative workaround, and on mobile it has a real limitation: because the screen list lives in app code, changing which screens are recorded requires shipping a new app release.
What this issue is really asking for is remote-config-driven screen recording — the mobile equivalent of web's URL trigger conditions: configure which screens to record/ignore in the PostHog UI, delivered to the SDK via remote config, with no app release needed.
That's net-new, coordinated work:
remote config payload changes to carry screen-name trigger conditions
UI changes in PostHog to configure them (cc @PostHog/team-replay)
per-SDK support to honor them (iOS / Android / React Native / Flutter)
Keeping this open to track the remote-config version — the documented manual approach above is the interim.
Activity
turnipdabeets commentedon Jul 10, 2026
closed for PostHog/posthog.com#18377
turnipdabeets commentedon Jul 10, 2026
Reopening and reframing this one.
The manual way to control which screens get recorded — wiring
start/stopSessionRecordingto navigation — is now documented for all four mobile SDKs:👉 https://posthog.com/docs/session-replay/how-to-control-which-sessions-you-record#programmatically-start-and-stop-recordings
But that's only the imperative workaround, and on mobile it has a real limitation: because the screen list lives in app code, changing which screens are recorded requires shipping a new app release.
What this issue is really asking for is remote-config-driven screen recording — the mobile equivalent of web's URL trigger conditions: configure which screens to record/ignore in the PostHog UI, delivered to the SDK via remote config, with no app release needed.
That's net-new, coordinated work:
Keeping this open to track the remote-config version — the documented manual approach above is the interim.
[-]Screen by screen basis recording[/-][+]Session replay: record/ignore screens via remote config[/+]