AI Model Wiki

    Skip to main content
    12 min read
    Lesson 3 of 5

    Building Edge AI Applications

    From the course AI for Edge Computing

    Deploying edge AI requires end-to-end thinking — from data pipeline to model serving to device management.

    Edge Inference Pipeline

    A typical edge AI application pipeline:

    1. Sensor Input — camera, microphone, accelerometer, or other sensors capture data
    2. Preprocessing — resize, normalize, and format input data on-device
    3. Model Inference — run the optimized model on the edge accelerator
    4. Post-Processing — interpret model outputs (NMS for object detection, etc.)
    5. Action — trigger alerts, control actuators, or store results
    6. Edge-Cloud Sync — periodically upload aggregated results or edge cases

    Computer Vision at the Edge

    Most common edge AI workload:

    • Object Detection — YOLO, SSD, and EfficientDet optimized for edge
    • Image Classification — MobileNet, EfficientNet-Lite, and custom models
    • Pose Estimation — MediaPipe and MoveNet for real-time body tracking
    • OCR — on-device text recognition for document scanning
    • Face Detection & Recognition — privacy-preserving facial analysis without cloud

    Audio & Speech at the Edge

    On-device audio processing:

    • Keyword Spotting — always-on wake word detection (< 500KB models)
    • Speech Recognition — on-device ASR (Whisper.cpp, Vosk)
    • Speaker Identification — verify identity from voice on-device
    • Sound Classification — detect events (glass breaking, gunshot, machine anomaly)

    NLP at the Edge

    Running language models on devices:

    • On-Device LLMs — Gemma 2B, Phi-3 Mini, and Llama 3.2 on smartphones
    • Text Classification — sentiment analysis and intent detection locally
    • Smart Reply — on-device suggestion of quick responses
    • Translation — offline translation using compact language models

    Over-the-Air (OTA) Model Updates

    Keep edge models current:

    • Version management for model files across device fleet
    • A/B testing new models on subsets of devices
    • Rollback capability if new model underperforms
    • Delta updates to minimize download size
    • Conditional updates based on device capability and connectivity

    Named Example: Tesla's fleet of vehicles uses OTA updates to deploy improved perception models, autopilot capabilities, and energy management algorithms to millions of cars simultaneously — treating edge AI model deployment as a continuous software delivery problem rather than a hardware upgrade cycle.

    Best Practice: Implement model shadowing (running the new model alongside the current model without using its output) on a subset of edge devices before a full fleet rollout. Shadow mode reveals real-world accuracy issues that synthetic test datasets miss.

    Common Pitfall: On-device NLP models often fail on text in non-Latin scripts because they were trained primarily on English and Western European text. If your edge application serves multilingual users, evaluate language coverage explicitly rather than assuming multilingual capability.

    Key Takeaways

    • •Edge pipelines span sensor input to inference to edge-cloud sync
    • •YOLO and MobileNet are workhorses for edge computer vision
    • •On-device LLMs like Gemma 2B and Phi-3 run on modern smartphones
    • •OTA model updates keep edge AI current across device fleets
    • •Audio AI enables keyword spotting in under 500KB of model size
    0 of 5 lessons marked complete

    Progress is kept in this browser only.