January 1, 2026
Browser Wars: Sushi Edition
iOS allows alternative browser engines in Japan
Apple opens the door to non-Safari browsers—only in Japan
TLDR: Apple now permits non-Safari browser engines on iOS—but only for Japan, and only under strict security rules. Comments erupted, arguing it’s a grudging, limited move, debating Apple’s memory-safety mandate, and calling for global change or a switch to privacy-first phones.
Apple says iOS 26.2 will let Japan-only apps use non-Safari browser engines, with access to speedy tech like just-in-time compilation and multi-process support. But there’s a catch: strict rules galore, from passing web standards tests (wpt.fyi, Test262) to using memory-safe languages and shipping fast security fixes.
Cue the comment section turning into a courtroom. The loudest chorus: “This isn’t real freedom—just a tiny, gated exception.” One user put “allows” in scare quotes, accusing Apple of doing everything possible to keep things mostly the same. Another asked the spicy question of the day: Would Apple’s own Safari engine even meet its memory-safety rule? Isn’t WebKit written in C++? Meanwhile, the geopolitics angle popped off—“Why only Japan? What forced this?”—as folks speculated about local competition pressure.
On the other end, privacy crusaders went nuclear, urging everyone to ditch Apple and Google for GrapheneOS, LineageOS, or even Linux phones, calling mainstream devices “instruments of mass surveillance.” The meme crowd had a field day with “Browser Wars: Bento Edition” jokes and “Safari the hall monitor” edits. A few security-minded commenters said the rules sound sensible, but most read it as Apple moving only because it had to—and only as far as it must.
Key Points
- •Apple will allow alternative browser engines in iOS 26.2+ for users in Japan in two app categories: dedicated browsers and in‑app browsers from engine stewards.
- •Access requires the Web Browser Engine Entitlement and developer authorization after meeting functional, security, and program requirements.
- •Apple will provide authorized developers system technologies such as JIT compilation and multiprocess support.
- •Functional compliance includes passing industry test suites, including at least 80% of Test262 on iOS/iPadOS/Mac (Apple silicon), and meeting thresholds even without JIT (e.g., Lockdown Mode).
- •Security obligations include secure development practices, public vulnerability disclosure and fix timelines, transparency on resolved issues, modern TLS support, and CA/Browser Forum participation for non‑SDK root stores.