Repository navigation
💡 AI-powered phone-camera Varroa mite counting with closed-loop treatment decision support #506
Replies: 1 comment
Weekly UpdateWhat ChangedBroodMinder launches BeeTV with AI-powered Varroa detection. BroodMinder shipped BeeTV — a mounted camera system for real-time hive observation including automated varroa mite detection via AI. ~100 units expected deployed by mid-2026. This validates the market demand for camera-based mite counting but uses a dedicated mounted camera, not a phone camera. BroodMinder's approach is complementary (always-on monitoring) rather than competitive (point-of-inspection phone capture). React Native ExecuTorch production-ready. ExecuTorch (by Software Mansion, Meta, and Expo) enables on-device PyTorch model inference within React Native apps. Pre-built hooks include On-device AI hardware maturing. Modern phones now have 70+ TOPS NPUs and 8-24GB unified memory. Apple Core AI (WWDC 2026) opened the on-device inference engine to third-party developers. Practical computer vision on a phone — without cloud calls — is no longer theoretical. Colony loss context reinforces urgency. Mistimed varroa treatments identified as the #1 driver of the 55.6% record colony losses in 2024-25 (improved to 39.9% in 2025-26). Accurate mite counts are the input that determines treatment timing — making this feature directly impactful on colony survival rates. Updated Assessment
Feasibility remains med: the inference infrastructure is ready (ExecuTorch hooks, hardware NPUs), but the varroa detection model itself requires training data — labeled images of mites on bees from phone cameras under field conditions. BroodMinder's BeeTV dataset is proprietary. Urgency increased due to the colony loss data directly linking mite count accuracy to survival outcomes. RecommendationAdvance with phased approach. Phase 1: Integrate ExecuTorch infrastructure and validate inference performance with a generic object detection model. Phase 2: Partner with a university bee lab (e.g., Auburn, Oregon State — the colony loss survey leaders) to build a labeled training dataset from alcohol wash and sticky board photos. Phase 3: Train and deploy the varroa-specific model. BroodMinder's BeeTV validates demand but their mounted-camera approach is complementary, not competitive — Broodly's phone-camera approach serves the 60%+ of beekeepers who don't have dedicated hardware. Generated by weekly feature ideation scan — 2026-08-31 |
Uh oh!
There was an error while loading. Please reload this page.
Summary
Enable beekeepers to photograph sticky boards or brood frames during inspections and receive instant AI-powered mite counts with infestation percentages and confidence scores. Unlike standalone counting tools (HiveLog AI, BeeScanning, VarroDetector), this integrates directly into Broodly's recommendation engine to produce treatment decisions with action + rationale + confidence + fallback — closing the loop from observation to decision in one zero-tap voice-triggered flow.
Market Signal
Phone-camera varroa counting is now production-ready across multiple competitors: HiveLog AI counts mites from brood-frame photos with confidence scores, BeeScanning uses phone camera AI, and VarroDetector offers free deep-learning sticky board analysis. BroodMinder is shipping automated hardware-based counting via BeeTV (~100 units mid-2026). However, no competitor integrates mite counts into a decision-support engine that produces contextualized treatment recommendations considering colony history, regional resistance patterns, and seasonal timing. The counting market is fragmenting into standalone tools; the integration opportunity remains open.
User Signal
Treatment timing is the #1 decision anxiety for beginner beekeepers (PRD user journey: Hannah must decide whether to feed, treat, or wait). Varroa destructor is the single largest driver of colony losses. The PRD's recommendation contract (action + rationale + confidence + fallback) is architecturally ready to consume mite count data as a high-weight input signal. The existing Vision AI pipeline (Vertex AI) in the architecture provides the inference infrastructure.
Technical Opportunity
The architecture already includes Vertex AI for inspection photo analysis (
architecture.md: Gemini Vision for inspection photo analysis), media upload via signed URLs to Cloud Storage, and async processing via Pub/Sub. The recommendation engine'sExplainableRecommendationcontract can consume mite count data directly. On-device inference via ExecuTorch (already tracked in Discussion #382) could enable offline counting. Voice command "check mites" triggers camera → AI count → recommendation in one continuous zero-tap flow.Assessment
Adversarial Review
Strongest objection: Phone-camera counting accuracy varies with photo quality, lighting, and sticky board condition. If the count is wrong, the treatment recommendation is wrong — potentially worse than no recommendation at all.
Rebuttal: This is exactly why the confidence score matters. The system communicates confidence explicitly ("Based on this photo, I estimate 3-5 mites per 100 bees with MODERATE confidence"). Low-confidence counts produce conservative, safety-first recommendations with fallback guidance for manual verification. The recommendation engine already handles confidence-aware fallbacks — this is a core architectural principle, not an afterthought. Users always see the evidence and can override.
Suggested Next Step
Create a technical spike story evaluating Vertex AI Gemini Vision accuracy on sticky board and brood frame photos. Define the integration contract between the Vision AI mite count output and the recommendation engine's treatment decision input. Benchmark against HiveLog AI's published accuracy metrics.
All reactions