Hacker News
Show HN: Helium Browser for Android with extensions support, based on Vanadium
1. desktop-style extensions: natively install any extensions (like uBO) from the chrome web store, just toggle "desktop site" in the menu first.
2. privacy/security hardening: applies the full patch sets from Vanadium (with Helium's currently wip).
Means you get both browsers' excellent privacy features, like Vanadium's webrtc IP policy option that protects your real IP by default, and security improvements such as JIT being disabled by default, all while being a reasonably efficient FOSS app that can be installed on any (modern) android.
It's still in beta, and as I note in the README, it's not a replacement for the full OS-level security model you'd get from running the GrapheneOS Vanadium combo. However, goal was to combine privacy of Vanadium with the power of desktop extensions and Helium features, and make it accessible to a wider audience. (Passkeys from Bitwarden Mobile should also work straight away once merged in the list of FIDO2 privileged browsers)
Build scripts are in the repo if you want to compile it yourself. You can find pre-built releases there too.
Would love any feedback/support!
reckless
|next
[-]
Combined Obtainium it's easy to keep it updated. https://github.com/ImranR98/Obtainium
imcritic
|next
|previous
[-]
That would raise the value of that project quite a lot (at least for me, but I feel like there are others, thinking similarly).
Please, push it to F-Droid!
Lucian6
|next
|previous
[-]
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.
sphars
|next
|previous
[-]
maxloh
|next
|previous
[-]
Some Chromium builds has that: https://chromium.woolyss.com/#google-api-keys
superasn
|next
|previous
[-]
Without updates, many sites will likely stop working with it soon.
Kiwi had some great features, like disabling AMP mode, rearranging the Chrome Store for mobile, and customizable tab layouts, etc. These features might interest others as well.
vrinsd
|next
|previous
[-]
Have you thought about merging your efforts with ungoogled-chromium (Android)?
There USED to be an ungoogled-chromium for Android (circa v88 chrome, the APK is still available for download) that also allowed extentions.
xrd
|next
|previous
[-]
Edit: hard to find where to get this browser. Do I need to build it myself?