PostHog / PostHog/posthog-flutter
Session replay: support v2 trigger groups (conditional recording)
Open
Nobody has claimed this yet.
enhancement
Session Replay
- Dominant language
- Dart
- Stars
- 97
- Forks
- 85
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Description
Mobile tracker for PostHog/posthog#35661 (Conditional Recording 3000). The replay trigger config is getting a v2 shape, and the mobile SDKs need to support it:
- multiple trigger groups, e.g. (20% sampling + error event) or (linked flag + url)
- minimum duration moving inside a group
- per-SDK matching, e.g. 40% sampling on web and 33% on mobile
- more trigger types on non-web SDKs (event and URL/screen triggers)
- debug properties, so conditional recording can be debugged outside web too
Sibling SDK issues:
- iOS (PostHog/posthog-ios#775)
- Android (PostHog/posthog-android#712)
- Flutter (this issue)
- RN (PostHog/posthog-js#4595)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Flutter SDK's existing replay trigger configuration and the linked iOS and Android sibling issues. Done means supporting the v2 trigger shape described here, including trigger groups, group-level minimum duration, per-SDK matching, additional event and URL/screen triggers, and debug properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100