Meta says Facebook for Android will soon use its own Chromium-based in-app browser engine, citing security and stability as reasons for its WebView alternative
Abner Li / 9to5Google :
Context & Ripple Effects
In 2015 Google positioned Chrome Custom Tabs as the faster replacement for Android's system WebView, letting apps open links in a Chrome-backed surface instead of maintaining their own renderer. Seven years later, Meta is going a step further: rather than relying on either WebView or Chrome-backed tabs, Facebook for Android will ship its own Chromium-based engine, with security and stability cited as the rationale.
The timing is awkward for that framing. Weeks earlier, researcher Felix Krause showed that Facebook and Instagram on iOS use a custom in-app browser that can observe every interaction, including keystrokes — coverage that put Meta's in-app browsing under a tracking microscope (the iOS in-app browser analysis). An Android move toward an even more self-controlled engine lands squarely in that debate.
First-order effects
- Facebook users on Android will have external links rendered by Meta's own Chromium fork rather than the system WebView or Chrome Custom Tabs, moving update cadence and rendering behavior from Google's release cycle into Meta's hands.
- Meta now maintains a second first-party browser engine deployment alongside its iOS in-app browser, deepening its control over how links opened from its apps execute.
Second-order effects
- Given the recent iOS tracking disclosures, Meta's 'security and stability' justification will be tested against what its custom engine can observe — privacy researchers and press will scrutinize the Android engine through the same lens applied to Instagram's iOS browser.
- Google loses a slice of the default in-app browsing surface it built Custom Tabs to win back from WebView, weakening the leverage of its own browser stack inside the largest Android app.
Third-order effects
- If major app platforms keep forking Chromium for in-app rendering, Android's web experience fragments from one OS-managed engine into per-app engines — shifting responsibility for security patching from Google to each app maker and complicating any future platform-level enforcement of browser behavior.
- Regulators and platform gatekeepers already focused on in-app browser transparency gain a concrete case: engine ownership, not just UI choice, becomes the thing that determines who sees user interactions inside an app.
The trend: Large consumer apps are replacing OS-supplied browsing components with self-maintained Chromium builds, trading shared-platform consistency for control over rendering, updates, and visibility into in-app sessions.