What's next:
- WebRTC integration for video calls
- Built-in barcode/QR code scanning
- Face detection hooks
That sounds to me like final application usages that should be independent from this project, which is just a HAL for camera access. Conflating the two into the same code seems to raise the bar incredibly high for the scope of this one, so not sure how that will work out. WebRTC alone is a very complicated beast, for which the camera acquisition is just a very small part.
ou were absolutely right about WebRTC complexity! Since that feedback, we've refocused CrabCamera on its core mission - desktop camera access for Tauri apps.
Changes made based on your feedback:
Removed WebRTC from core scope
Focused on clean camera capture API
Left streaming protocols to dedicated libraries
Current CrabCamera v0.3.0:
45/45 tests passing
Production-ready in Budsy plant identification app
Clean separation of concerns
Thanks for steering us toward better architecture!
