When building desktop or edge AI applications, the default instinct for many engineers is to run pip install opencv-python .
However, as your architecture matures toward lightweight, self-contained edge software (such as a PyQt6 GUI app running ONNX Runtime on CPU), third-party C++ wrappers introduce real operational friction:
Deployment Bloat: 40–50 MB binary wheels ( opencv-python-headless on Linux/Windows x64) that expand desktop installers.
Cold-Start Latency: Shared C++ library initialization delays during application startup.
Dependency Conflicts: Threading and event-loop clashes with native Qt backends.
In our project — Hawk Eye , an industrial AI edge application for monocular tire tread depth assessment — we enforced a strict rule: Zero CV-specific external dependencies (no OpenCV, SciPy, or Scikit-Image).…