PostHog / PostHog/posthog-android
Session replay: support v2 trigger groups (conditional recording)
Open
Nobody has claimed this yet.
enhancement
Session Replay
- Dominant language
- Kotlin
- Stars
- 90
- Forks
- 49
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 61
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 (this issue)
- Flutter (PostHog/posthog-flutter#545)
- 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
No Android files, tests, or entry points are named. Start by reviewing the existing Android session-replay trigger configuration, then compare the v2 requirements with PostHog/posthog#35661 and the sibling SDK issues; done means Android supports the listed trigger groups, matching rules, trigger types, minimum duration, and debug properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- analytics, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100