The overall licenses applying to GrapheneOS are unchanged. Vanadium will be using the same GPLv2-only licensing approach used by the Linux kernel. We didn't find it particularly fair that a project is including our code while we would be unable to use theirs even if we were willing to include GPLv3 code because they do not grant the exception we would need for linking the WebView with non-GPLv3 compatible apps in the OS. They included most of our code and lots of code we hadn't merged yet such as their content filtering implementation being based on the one done for GrapheneOS, per-site JIT toggle and much more. They were previously allowing us to use most of their code via dual licensing it. Blocking the upstreams from using their code is exactly what Bromite is doing. As part of using GPLv2 we require contributors authorize upstreaming code under the preferred upstream license, which only applies if it's accepted. GrapheneOS cares about being able to upstream code. Part of the reason for not offering them already is as follows: This will obviously be taking a back seat during the process of porting GrapheneOS to Android13 so is a Soon™ item. In the near future, we plan to add support for always incognito mode, content filtering (ad blocking, etc.), improved state partitioning, backup/restore, native autofill and many other features. Vanadium was previously primarily focused on security hardening but we plan on adding assorted privacy and usability features. The second paragraph addresses the two easential features you mentioned:

If you want to use Bromite that is your perogative but to clarify Vanadiums strengths please take some time to familiarise yourself with the documentation on the website:

The whole which is better argument is slightly misguided as the whole point of the OS is that it is for everyone, which in turn means, within the scope of the project enabling users to make choices that fit their own needs and use cases.

Brave incognito tab