Re:Show HN: Helium Browser for Android with extensions suppo...
by Lucian6 on Sunday October 26, 2025 @11:31PM
(#45717151)
I've been digging into Vanadium's extension support implementation and this looks like a solid approach for Android. The key challenge we faced with WebExtensions on mobile was the memory footprint - each extension runs in its own process which can add 30-50MB of overhead per extension on resource-constrained devices.
Curious how you're handling the isolation/sandboxing model here? The standard Chrome approach of site isolation + process-per-extension becomes pretty heavy on mobile. Have you considered using a shared process model with context isolation instead? We found that careful use of V8 contexts could give similar security guarantees with ~70% less memory overhead, though it required some tricky IPC handling between the extensions and main browser process.
Also worth noting that the WebExtension manifest v3 transition adds some extra complexity for mobile browsers - particularly around the service worker lifecycle and background page limitations. Would love to hear how you're approaching that migration path.
Curious how you're handling the isolation/sandboxing model here? The standard Chrome approach of site isolation + process-per-extension becomes pretty heavy on mobile. Have you considered using a shared process model with context isolation instead? We found that careful use of V8 contexts could give similar security guarantees with ~70% less memory overhead, though it required some tricky IPC handling between the extensions and main browser process.
Also worth noting that the WebExtension manifest v3 transition adds some extra complexity for mobile browsers - particularly around the service worker lifecycle and background page limitations. Would love to hear how you're approaching that migration path.