Feature #529

Design Privacy Browser for other mobile environments

Added by Rayleigh Rayleigh 8 months ago. Updated 6 months ago.

Start date:
Due date:
% Done:


Estimated time:


I know this is a looong haul, but since there are at least two Linux phones coming out soon, the possibility of making a Linux ARM version of PB could be interesting



Updated by Soren Stoutner 8 months ago

  • Assignee set to Soren Stoutner

I have been thinking a lot about other platforms. Each codebase is going to end up with its own section in Redmine, but I don't intend to create those sections until development begins (because there are a lot of possible options, and I don't know which path I am going to go down yet).

I have written a bit about this topic in other places, like the roadmap, but I will add a few thoughts here as well.

The next platform I intend to develop for will be the desktop. Originally, I was planning to wait until after the 4.x series was complete before starting development for desktop. But I am now thinking that I might move that up and start desktop development after the completion of the 3.x series.

My current thought is to develop the desktop codebase using the QT framework (this is the same framework used by KDE). My primary target would be for Linux, but I would also build and test extensively for Windows. QT can also be compiled for macOS, and I would release on that platform as well as long as it didn't require too many customizations.

Mobile Linux platforms that ship the QT libraries could also run the desktop version, but it is unlikely that the UI would work well on a phone sized screen. Rather, after getting the desktop version into decent shape, I would likely need to build a separate version that works well for mobile Linux. In fact, because each mobile platform is so unique, I might have to build a separate app for each platform that takes off. Hopefully there aren't too many of them.


Updated by Rayleigh Rayleigh 8 months ago

If you aren't dead-set on qt yet, investigatimg libhandy might interest you, it's a library that works well at making desktop GTK applications work on mobile seamlessly.


Updated by Rayleigh Rayleigh 8 months ago

Also, another thing to consider would be using Gecko/Quantum instead of Chromium as a rendering engine, since there already are some more privacy-oriented desktop browsers based on Chromium (Brave, Ungoogled Chromium), yet I haven't heard of a Gecko/Quantum-based one that wasn't a fork of Firefox.


Updated by Soren Stoutner 8 months ago

Before actually implementing a release for another platform I intend to look at the options more closely, but at this point I think it is unlikely that I would base it on GTK.

I wrote a fairly long explanation about why I don't feel that GeckoView is the appropriate choice for Privacy Browser on Android. Although not everything I said there applies to other platforms, there are a lot of synergies involved in basing all the platforms off the same rendering engine.

My current plan is to base the desktop version on QtWebEngine, which is fairly similar to Android's System WebView.


Updated by Soren Stoutner 6 months ago

  • Subject changed from Linux ARM version? to Design Privacy Browser for other mobile environments

Also available in: Atom PDF