WICG / WICG/shape-detection-api
Add binary size information to explainer (README.md)
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 316
- Forks
- 39
- Avg merge
- 8d 3h
- Merged PRs (30d)
- 1
Description
Consider adding information about native-apps alternatives for shape detection, e.g. ZXIng in Android, and how they fare binary-size wise with the OS/Hw alternatives and with the JS versions.
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 reading README.md and locate the explainer content on native-app alternatives and shape detection. Research ZXing on Android alongside the OS, hardware, and JavaScript alternatives mentioned in the issue, then document their binary-size trade-offs in the README. Done means the comparison is clear and included in the explainer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- documentation, mobile-dev
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100