3 ms·
If you're interested in browser extensions on mobile, we're building a way to deliver any extension to any mobile device, without any download. The way it work
by keepamovin 3y ago
If you're interested in browser extensions on mobile, we're building a way to deliver any extension to any mobile device, without any download.
The way it works is the extension runs on a browser on the server, which is then streamed to the device, and usable through any regular mobile browser, such as Safari, Chrome, Brave, Firefox, etc.
This browser technology removes the restriction on extensions on mobile, as well as limits some (but not even close to all) of the security risks of extensions. In a real sense it enables: cross-browser extensions.
While it sounds promising, it suffers from at least four major drawbacks.
1. We still need to build a shim of the Chrome extensions API: https://github.com/BrowserBox/BrowserBox/issues/242 https://github.com/BrowserBox/BrowserBox/issues/242
2. Rather than having many extensions on a single browser, this effectively serves a single extension from a given web endpoint, but crucially permits you to browse anywhere from there with that extension loaded.
3. While he have future plans for a "store", there is currently no store. This means there is no central place to discover extensions, and also no central authority to vet and restrict them regarding security.
4. You have to consider infrastructure, at least for now before we launch a managed service for this. While the application is easy to set up, maintaining a large fleet could bring additional workload that may limit your distribution, or increase your costs.
If you believe there is something worthwhile in exploring these avenues beyond existing browser technologies, and pushing the applications of the browser and the web further than they have been pushed before (at least in this meta sense), I encourage you to come get involved. We're open source and happily accept contributions that align with the project's goals: https://github.com/BrowserBox/BrowserBox https://github.com/BrowserBox/BrowserBox
But it's good to see Firefox is finally implementing their long held goal to do this! This will probably cause other vendors to do the same, I imagine? What would be the reasons that vendors would resist bringing extensions to mobile?
- remram 3y agoMaybe this should be its own Show HN, a little long for a "comment" on another mobile browser.
- keepamovin 3y agoYou're suggesting that it's made as a comment dishonestly, and that you can decide what's too long or where it should be placed? Well, luckily you can't. But, anyway, it's not a little long, it's perfect! Hahaha :) I get if you feel that way about it, but it's not how it is. So, it's good that you don't get to decide that for me! Hahahaha :) In other words: "Should" may be that way for you, but not for me. More generally, you could consider that the comment you're replying to adds value to the discussion, but yours doesn't. I mean, I get if you don't like promotion and that's ok -- but this is less that and more exploring some technical possibilities that are highly relevant to the OP. But anyway, if you dislike it, that's not about me at all, that's just about you. You don't need to pretend it's "should" about somebody else, now do you, right? :)
- g-b-r 3y agoThis seems to be in practice simply using a browser in a remote vm, bye bye privacy and security if you're not hosting it yourself
- keepamovin 3y agoExactly! The lack of privacy and inherent security risks involved in trusting a SaaS provider such as Cloudflare Browser Isolation, or Ericom, or any of the other RBI providers is a real and valid concern. That's one of the reasons we created BrowserBox, and what distinguishes BrowserBox from all its competitors: it is self-hosted, and open source. So not only can you run it on infra you trust, but you can vet all the source code to ensure it meets your privacy and security needs. That being said the privacy/security & trust vs convenience trade off of using SaaS is acceptable for some customers, and we are opening up a SaaS version of our product soon, diversifying away from only "on-prem" deployments.