Witnio.
Web/Mobile Assurance

Low-end Device Check

Measure your app or site on real low-end Android hardware, not an emulator.

  • lowend_check
Coming soon
$99.00/mo
  • 1 app
  • 80% warning / 100% soft-stop overage policy, per plan
Notify me
01 — The problem

The problem

Emulators don't faithfully reproduce behavior under the constrained memory/CPU of a real low-end phone.

Who it is for

Any company whose app/web must work on low-end Android phones (markets where most real users have limited hardware) and has no hardware of its own to test on.

02 — What you send us

What you send us

FieldFormatValidation
url or package_namehttp(s) URL, or Android package nameExactly one of the two is required, never both
min_tierlow / mid / highDefaults to low; compared against device_tier_observed as meets_min_tier
cold_startBooleanDefaults to true — measures am start -W TotalTime/WaitTime
03 — What runs

What runs

  • The worker runs the check on a real low-end Android device (never an emulator): device profile, load/cold-start timing, PSS memory, jank frames, and any FATAL EXCEPTION/ANR observed via a logcat window.
  • Fault profiles covered by the harness: network_loss, adb_loss, sim_anomaly, reboot, ui_change (service_restart is not yet registered — apply()/restore() unimplemented in fault_injection.py, a pre-existing gap).
  • No formal backtests have run against the real device yet (BLOCKED_HARDWARE) — the probe exists but has 0 measured runs today.
04 — What you get

What you get

json
{
  "status": "ok",
  "detail_json": { "device_tier_observed": "low", "meets_min_tier": true, "pss_kb": 118432, "cold_start_total_ms": 2140, "janky_frames_pct": 3.1 },
  "screenshot_path": "evidence/2026-09-23/lowend/run_9a4d.png",
  "failure_class": null,
  "recovery_actions_json": null,
  "evidence_signature_json": {
    "signature": "b8c3...f0",
    "algorithm": "Ed25519",
    "key_id": "witnio-run-ed25519-2026-09"
  },
  "ran_at": "2026-09-23T14:02:11Z"
}
  • One MonitorRun per run
  • Screenshots
  • Timings
  • Evidence
  • Dashboard/API per plan
05 — Limits & quotas

Limits & quotas

Loading...

06 — Autonomy

Autonomy

Designed to run unattended end to end. Not yet measured: zero real backtest runs against the physical device today (BLOCKED_HARDWARE) — the check_type and probe exist, but autonomy has no measured figure yet.

07 — Compliance

Compliance

Evidence

No publishable claim yet for this service — backtests and real-world evidence are still being measured. See Known limitations below.

Verify evidence

08 — Known limitations

Known limitations

  • No formal backtests measured yet.
  • Measured today on a MID-range device until a real low-end device is added to the pool: every run honestly declares the observed device tier and whether it meets the minimum tier — a low-end result is never simulated.
  • Depends on the internal_research/low-end physical pool, currently limited in size.
  • Crash detection is a best-effort logcat-window scan, not a full stack-trace parser.
09 — FAQ
FAQ

Questions about this service

Not yet. No formal backtests or real-world samples exist yet, so it stays fail-closed until that changes.

Related guides

Ready for Low-end Device Check?

Notify meSee pricing