Android
AuraScore 91/100

On-Device Multimodal Runtime Verification Audit

Audit on-device vision-language models for Android NPU execution, memory budgets, and thermal stability.

Use this checklist when deploying compact multimodal foundation models onto consumer Android devices via LiteRT or ExecuTorch. It validates NPU delegate compatibility, sensor buffer allocation, and memory pressure limits.

Template

Role: Principal On-Device ML Android Architect specializing in edge vision-language models and hardware acceleration.

Context

  • Target NPU and SoC architecture: {{target_npu_soc}}
  • Vision-language model variant: {{vision_model_variant}}
  • Maximum runtime memory headroom: {{memory_headroom_mb}}
  • Model quantization and weight format: {{quantization_format}}
  • Target camera ingestion throughput: {{min_frame_rate_fps}}
  • Android CameraX image stream format: {{camera_stream_format}}

Task

Deliver an exhaustive technical verification checklist to evaluate the on-device inference pipeline of {{vision_model_variant}} on {{target_npu_soc}}, ensuring zero frame drops, strict memory compliance within {{memory_headroom_mb}}, and stable hardware acceleration.

Method

  1. Analyze NPU operator mapping and delegate fallbacks for {{vision_model_variant}} under {{quantization_format}}.
  2. Verify zero-copy buffer sharing between {{camera_stream_format}} and the vision encoder tensor input.
  3. Profile native memory allocations against the designated limit of {{memory_headroom_mb}} during concurrent token generation.
  4. Validate KV-cache management and paging strategies under prolonged conversational turns.
  5. Audit thermal throttling curve and sustained performance at {{min_frame_rate_fps}} over 15-minute operational sessions.
  6. Evaluate multi-threading and CPU affinity configurations for asynchronous tokenizer execution.
  7. Formulate pass/fail criteria for fallback mechanisms when NPU acceleration is unavailable.

Constraints

  • Checkpoints MUST specify explicit memory offsets, API boundaries, or native NDK flags.
  • Verification items MUST NOT accept synthetic desktop benchmark approximations.
  • All items must differentiate between fatal runtime blockers and non-critical performance optimizations.
  • The checklist must strictly cover edge inference without dependencies on remote cloud fallbacks.

Output format

  • Section 1: Hardware Acceleration and Operator Support (5 items)
  • Section 2: Memory Footprint and Direct Buffer Management (5 items)
  • Section 3: CameraX Ingestion and Tokenization Pipeline (4 items)
  • Section 4: Thermal, Power, and Graceful Degradation (4 items) Each item must follow the format: [ ] [CRITICALITY] Verification Objective: Concrete test procedure and pass criteria.

Self-review

  • Confirm all 6 input variables are directly referenced across the criteria.
  • Verify every checklist item has explicit, measurable pass/fail thresholds.
  • Ensure zero ambiguous guidance or generalized Android platform suggestions.
AuraScore breakdown
91/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification14/14 · Strong

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-android
image-multimodal-prompting
android
multimodal
on-device-ml