Leverage Compose semantic nodes when the debug tooling dependency isn't available
Open
- Dominant language
- Kotlin
- Stars
- 899
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
See https://blog.bitdrift.io/post/implementing-session-replay-android-compose
We could leverage SemanticNode in prod.
Contributor guide
Research direction
Start with the linked Bitdrift article, then locate the current Compose debug tooling dependency and the production UI inspection entry point. Determine how SemanticNode can be used when that dependency is unavailable. Done means production code can leverage Compose semantic nodes without requiring the debug tooling dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- devtools, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100