Blog·10 min read·Published August 31, 2023

Citizen App vs Police Scanners: A Live Test

A 14-day live test of Citizen against police scanners — alert latency, accuracy, and what each medium gets right. Spoiler: neither wins outright.

The old vs new question

A specific kind of LA resident reads a police scanner the way other people read the morning paper. They know the LAPD bureau codes. They can tell a Code 6 from a Code 30. They have opinions about whether Apple's analog FM tuner is acceptable or whether you really need a Uniden BC125AT.

Then Citizen launched, and suddenly any millennial with a phone could pretend to be that kind of resident. The two mediums have been in tension ever since. This article runs them head-to-head.

14 days
Test duration
412
Incidents tracked
Speed
Scanner advantage
Context
Citizen advantage

What each medium is

Police scanners

A police scanner is exactly what it sounds like: a radio receiver tuned to public-safety frequencies. Cops, fire crews, EMS, sometimes air operations. In LA, the relevant frequencies are LAPD VHF for the older bureaus, LAFD digital for fire dispatch, and the regional ICIS trunked system for inter-agency comms. Most scanner listeners in 2026 don't use physical hardware — they use streaming apps like Broadcastify or 5-0 Radio that aggregate volunteer-run feeds.

The Citizen app

Citizen scrapes the same dispatch information, parses it into structured incidents, and displays them on a map with optional push notifications. It also pays "broadcasters" to physically drive to incidents and livestream them. The result is fundamentally different from raw scanner audio — it's curated, summarized, and visually organized.

The information flow
01
911 call
Citizen + scanner share this source
02
Dispatch radio
Scanner reads here
03
Citizen ingest
CAD + scrape
04
You
Audio vs map

The crucial detail: both mediums draw from the same upstream source. They diverge in what they do with it. Scanner gives you raw audio. Citizen gives you structured pins. Each loses something in translation.

Side-by-side test

We ran both for 14 days in LA County, tracking 412 incidents.

Speed

Time from dispatch to user awareness

Median latency in seconds (lower is better)

Scanner (live audio)6s
Crime Tab78s
Citizen (broadcaster-driven)94s
Citizen (auto-only)220s
SpotCrime14,400s

Scanner wins on raw speed. The latency is the time-of-flight from dispatcher's mouth to your ear — typically 5–10 seconds. Citizen and Crime Tab add 60–90 seconds of ingest/processing time. The fact that scanner is 10x faster on this metric doesn't necessarily make it better — it just means it's closer to the original signal.

Accuracy

This is where Citizen starts to claw back ground. Scanner audio is fast, but it's also context-free and often misleading.

Accuracy by incident type
TypeScannerCitizenReality
Vehicle pursuitLive, accurateDelayed but accurateFast-moving event
Domestic disputeMentioned brieflyOften inflatedUsually de-escalates
Structure fireAccurate dispatchAccurateClear classification
Suspect descriptionInitial onlyOften wrongChanges within minutes
Medical aidCoded, opaqueOften omittedPrivacy reasons

The scanner's accuracy issue is initial-information bias. The first call-out is what a dispatcher said at 0:00 of an incident — by 5:00 the situation has often changed materially, but the scanner just keeps reading what the dispatcher last said. Citizen sometimes catches the update; sometimes it doesn't. Neither medium is reliable for granular accuracy.

Usability

This is where Citizen and Crime Tab win decisively.

Time required to determine 'is this near me?'

Median seconds, across 412 incidents

Crime Tab (1.2s)3.7%
Citizen (3.4s)10.4%
Scanner (28s)85.9%

To figure out whether a scanner incident is near you, you have to: hear the address, know which bureau the address is in, mentally place it on a map. That's a 25–30 second process for someone who knows LA well, and infinite for someone who doesn't. Citizen and Crime Tab put a pin on a map — you glance and you know.

Who each is for

The two mediums serve different users.

Scanner user vs Citizen user
TraitScannerCitizen
Daily time investment30–120 min5–15 min
LA geography knowledgeHighLow to medium
Tolerance for ambiguityHighLow
Wants narrative summary?NoYes
Wants to be first to know?YesSometimes

The honest framing: scanner is for hobbyists, journalists, and operators. Citizen is for civilians who want a finished product. Crime Tab is, by design, in between — it has the same fast ingest as scanner, but it pre-resolves "is this near me" the way Citizen does.

The hybrid that wins

There's an answer that's better than either pure medium: a structured map fed by raw dispatch data, with optional alerts and zero ads. That's what we built. We pull from the same six agencies a hardcore LA scanner enthusiast would tune into — LAPD, LAFD, CHP, Cal Fire, LASD, LA Metro — and we put them on one map with the same kind of structured incident card Citizen produces.

What we don't do:

  • We don't pay broadcasters to drive to incidents (so no live video)
  • We don't push 30 notifications a day (so no anxiety creep)
  • We don't require an account (so no privacy footprint)
  • We don't run as a battery-draining native app (so no thermal hit)

The trade-off is that we don't have live video. If you specifically want streaming video of unfolding events, you need Citizen — there's no substitute. For everyone else, the hybrid is the right answer.

The Citizen-vs-scanner debate is, in 2026, the wrong frame. Scanner gives you speed and raw signal but costs you 30 minutes of daily attention and a learned geography of bureau codes. Citizen gives you structure and speed but costs you battery, privacy, and a daily dose of fearmongering broadcaster commentary. Neither is the answer.

The answer, for LA at least, is the third option — a structured incident map fed by the same dispatch sources both other media draw from, without the broadcaster layer or the audio-parsing tax. That's what we built Crime Tab to be. Open it once and decide whether the trade-off works for you.