Find the right AI model for your Android device.

Measure your hardware. Predict inference with Meta AI. Benchmark locally. Compare results with real evidence.

A prototype built for the Meta Global AI Developer Hackathon — real on-device llama.cpp inference, never simulated numbers.

Official 2:55 hackathon demo published · Watch the extended 10:09 unedited Android demo published · Full technical walkthrough v1.1 published · v1.0 archive

EdgeFit AI Home screen on a Samsung phone: device overview with CPU, RAM, battery and thermal metric cards

Captured on-device real screenshot — status bar and time are from the original capture.

See EdgeFit AI in Action

Watch a 2-minute-55-second demonstration of hardware-aware model evaluation, real on-device inference, Meta-assisted reasoning, and evidence verification.

Player loads only when you press play. Watch on YouTube · Extended 10:09 unedited demo · Android APK pre-release


Why Android? Hardware decides.

Android phones span an enormous range of CPUs, memory, storage, and thermal behavior. A model that flies on one phone may crawl on another — so EdgeFit starts from your measured hardware, not a leaderboard.

What EdgeFit does

Hardware-aware model selection

Profiles your phone and recommends compatible local LLM candidates with explicit compatibility estimates.

Real on-device benchmarking

Runs genuine llama.cpp inference on the phone and records measured throughput with thermal and memory conditions.

Meta Muse Spark predictions

Predicts inference speed before each measurement, with uncertainty — then the phone checks the answer.

Predicted vs measured

Every prediction is stored first; error is computed deterministically by the host, never narrated by the model.

Agentic optimization, gated

Bounded experiment proposals with explicit approve / reject and a fixed attempt budget. Nothing auto-runs.

Privacy-first sharing

Results stay on-device until you approve per-submission sharing. Global aggregates publish only above quorum.

How EdgeFit AI Works

One picture of the whole system — from your phone to public evidence. This is Walkthrough v1.1, Fig 02, drawn from the shipped sources:

EdgeFit AI system architecture diagram: on-device app and native inference, optional Meta Muse Spark prediction, governed Cloudflare backend, public dashboard
System architecture — tap the diagram to view it full size. On-device contribution is implemented; public publication is proposed, gate B off.
  1. 1Read actual device constraints — CPU, memory, ABI, thermal state.
  2. 2Evaluate model suitability against the offline catalog, with explicit uncertainty.
  3. 3Run native llama.cpp inference benchmarks on the phone.
  4. 4Validate and preserve each measurement as hashed on-device evidence.
  5. 5Optionally use Meta Muse Spark for bounded prediction and owner-approved experiments.
  6. 6Contribute evidence to the Global network only with explicit consent.

Read the Definitive Walkthrough v1.1

Hardware-aware, like the app

The Android app starts from your device, not from a leaderboard. The same idea, on the web:

Example device profile DEMONSTRATION

Illustrative values for a phone of this class — not measured from your browser, which cannot see your hardware.

Device
SM-S908U class
CPU cores
8
Total RAM
≈7.1 GB visible (example)
Free memory
~1.8 GB (illustrative, varies live)
Thermal
nominal (illustrative)
ABI
arm64-v8a

Try the model-fit check DEMONSTRATION

Pick a model size to see how EdgeFit reasons about fit before any benchmark runs. Sizes are public model facts; memory figures are illustrative. This is arithmetic, not a measurement — EdgeFit shows throughput only from real qualified runs.

The Android workflow

  1. 1Select a GGUF model file on the phone.
  2. 2Configure inference: context, threads, prediction length.
  3. 3Run a physical benchmark; results stay on-device.
  4. 4Review measured throughput per session.
  5. 5Optionally contribute with explicit consent (genuine uploads flowing under consent approval — see live counts on the dashboard).

App sections, as shipped: Home · Benchmark · Sessions · Agent · Settings.

EdgeFit AI Benchmark screen: numbered Model, Configure and Run sections with model file and config actions

Captured on-device real screenshot — status bar and time are from the original capture.

Meta Muse Spark, honestly scoped

EdgeFit uses Meta's Muse Spark model to help analyze validated evidence: predictions before measurement, evidence-grounded follow-ups, and bounded optimization proposals — every one behind explicit human authorization. A validated tool request runs one fixed read-only query over local SQLite, and the model reasons over the returned rows. No live model outputs are shown on this site, and nothing here implies endorsement by Meta.

More than a static demo: technical evidence

Six-run physical study measured

Galaxy S22 Ultra, fixed workload: 4-thread median 16.52 tok/s vs 8-thread median 10.49 tok/s (n=3 each, exploratory, one device). Muse correctly abstained rather than guess beyond the evidence (fabricated-citation rate 0.0). Full artifacts, frozen manifests, and methodology live in the source repository, with reproducible offline test suites.

Global evidence, gated by proof

The long-term goal is a global network where only verified, consented, comparable phone measurements count. Genuine contributions are flowing (see live counts on the dashboard), but zero verified global aggregates are published yet. The evidence status page tracks exactly what exists and what publication requires.

Provenance honesty

All EdgeFit AI source in this repository is new work started October 26, 2026, for this hackathon. Honey LLM and BeeBench are pre-existing independent projects; EdgeFit does not reuse their code or present their results as its own.