Privacy Browser Android

I am generally not in favor of options that modify the way the GUI works. They add a lot of complexity to the code and have a heavy maintenance burden over time.

I have made a few exceptions to that principle when there have been significant reasons for doing so. For example, I have implemented the ability to have the app bar on the top or the bottom, and to enable a light and dark theme.

Being able to change which icons appear in the app bar would be fairly difficult, probably a lot more difficult than someone not familiar with the codebase would imagine. It is a lot more complex than simple toggling how many icons can appear in the bar, which is what the current setting does.

As a more general answer to your question, I would suggest you read over Privacy Browser's Design Guidelines, which probably contain the answer to many other things you are curious about.

https://www.stoutner.com/privacy-browser-design-guidelines/

Soren Stoutner wrote in RE: App bar button options?:

Being able to change which icons appear in the app bar would be fairly difficult

I mean to keep the icon the same but change what happens when you use it. The look of the interface won't change at all. :)

That would be very complicated. Additionally, not changing the icon to indicate what it does would represent an unacceptable GUI design in my opinion and would not be something I would ever inflict on Privacy Browser's users.

not changing the icon to indicate what it does

It would do what the user wants. It would be up to the user to decide. :)

From time to time I receive requests from users to create a bad GUI design in Privacy Browser. I consider Privacy Browser's GUI design to be one of its strongest benefits, and far superior to any other browser I have used on Android. One of the things I have noticed about bad GUI recommendations is that the person making them has not spent much time considering how other people use Privacy Browser, or how their suggestions would make life more difficult for other users.

As a developer, I cannot make a design decision that only considers the need of one user, and I cannot make a design change that benefits one user but makes life for difficult for other users. Some of these include.

1. Designs that make Privacy Browser more confusing for new users.
2. Designs that make Privacy Browser not work well for all common workflows.
3. Designs that are unintuitive.
4. Designs that aren't in conformity with the Core Privacy Principles or the Design Guidelines.

There is so much bad software out there with bad interfaces and bad user experiences. Part of what it means to be the principle developer of Privacy Browser is to say no when people recommend changing Privacy Browser in a way that would mimic the bad design decisions of other software.