Skip to main content

Case Studies Overview

This series is distinct from the Extension API reference and the Dashboard Component API reference — those cover "what the API looks like and what it can do." This series focuses purely on real engineering practice: why a design was chosen, what pitfalls were hit, and how engineering standards are applied on the ground. Every case is selected from a real NeoMind ecosystem repository and audited by hand into a reproducible engineering write-up.

The 7 Cases at a Glance

#CaseTypeDifficultySizeKey Value
1weather-forecastData extensionBeginner~700 LOCFirst-extension template (HTTP fetch + periodic metrics + React frontend)
2yolo-device-inferenceAI inferenceIntermediate~1950 LOCLazy model loading / cross-session reuse / device camera integration
3yolo-videoStreaming extensionIntermediate~3900 LOCstream session + video-frame processing + VLM dashboard interop
4onvif-bridgeProtocol bridgeIntermediate~2700 LOCIP camera / standard protocol integration (parallels NeoEyes)
5uink-rms-bridgeProtocol bridgeIntermediate~2250 LOCProduction-verified bridging
6metric_cardDashboard componentBeginner~400 LOCComponent template (value card + threshold / trend / unit)
7ne101_cameraExtension + component interopFlagship~2500-3500 LOC (8 sub-pages)End-to-end deep tutorial

Reading Paths

Pick the shortest path for your role and goal:

  • Path 1 (Newcomer): 167 — Build intuition with the simplest extension and component, then tackle the end-to-end flagship case.
  • Path 2 (AI Engineer): 237 — From single-frame inference to video-stream processing, then full product integration.
  • Path 3 (Industrial Integrator): 457 — Two protocol-bridge cases as foundation, then a camera-grade product integration.
  • Path 4 (Component Developer): 67 → any extension case — Master the component paradigm first, then learn how to interop with extensions.

Version Alignment Table

Case code is aligned with the source repository's release; the audit locks to a specific commit.

CaseSource repo versionSDK versionLast audit
1 weather-forecastv2.7.6SDK 0.62026-06-22
2 yolo-device-inferencev2.7.6SDK 0.62026-06-22
3 yolo-videov2.7.6SDK 0.62026-06-22
4 onvif-bridgev2.7.6SDK 0.62026-06-22
5 uink-rms-bridgev2.7.6SDK 0.62026-06-22
6 metric_cardv1.7.02026-06-22
7 ne101_camerav2.14.92026-06-22

Note: since the last audit the source repository has kept evolving — the current versions are weather-forecast 2.7.7, yolo-device-inference / yolo-video 2.7.8, and ne101_camera 2.14.12. Each case page's audit-time snapshot is pinned by the banner at the top of that page.

A case audit is triggered when the source repository cuts a release (manual, not automated).

Component Source Format Note

NeoMind Dashboard Components ship as hand-written IIFE JavaScript — the file is named bundle.js, but it is not a compiled artifact; it is human-authored source.

Conventions:

  • Runtime dependencies are injected via var React = window.React + var jsx = window.jsxRuntime.jsx (React / JSX runtime are provided by the host page).
  • Full comments and reasonable line breaks are preserved; readability is close to plain source code — you can read it directly without a source map.
  • Current sizes: metric_card is 328 lines, ne101_camera is 2036 lines.

Therefore the "key code walkthroughs" in cases 6 / 7 point directly at specific line numbers in bundle.js — readers can open the source file and follow along.

Further Reading


Last updated: 2026-09-08