PostHog / PostHog/posthog-android
Rage touch detection
Open
Nobody has claimed this yet.
enhancement
Product Analytics
Session Replay
- Dominant language
- Kotlin
- Stars
- 90
- Forks
- 49
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 61
Description
Problem Statement
Similar to https://posthog.com/docs/product-analytics/autocapture#autocaptured-events
- Android (this issue)
- iOS
- RN (https://github.com/PostHog/posthog-js/issues/3811)
- Flutter (https://github.com/PostHog/posthog-flutter/issues/425)
Solution Brainstorm
No response
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 linked PostHog autocapture documentation and the related iOS, React Native, and Flutter issues. The Android issue has no named files, tests, implementation entry point, or concrete acceptance criteria, so the first step is to clarify the Android behavior and scope; done would require an agreed design and implementation for rage touch detection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- analytics, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100