PostHog / PostHog/posthog-android
Element interactions auto capture support
Open
Nobody has claimed this yet.
Autocapture
enhancement
Product Analytics
- Dominant language
- Kotlin
- Stars
- 90
- Forks
- 49
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 61
Description
Description
- RN (https://posthog.com/docs/libraries/react-native#autocapture)
- iOS (https://github.com/PostHog/posthog-ios/issues/179)
- Android (this issue)
- Flutter (https://github.com/PostHog/posthog-flutter/issues/122)
For Jetpack compose, we might need a view modifier approach like postHogAutocapture() that composables are annotated with.
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 referenced Amplitude Kotlin AutocaptureGestureListener and the linked PostHog React Native, iOS, and Flutter work. Then inspect how this Android SDK handles Jetpack Compose interactions and determine whether a postHogAutocapture() modifier is needed. Done means element interactions are automatically captured for the intended Android surfaces.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100