This is pretty misleading due to its brevity, an attacker on the same network can determine what website you're going to but not the content being exchanged. A VPN moves the threat of having your browsing destination determined to the VPN provider from the local network.
That said, modern WiFi encryption does prevent other devices on the network from eavesdropping, so the attacker would have to employ a more involved attack (e.g. ARP spoofing) in order to even see the destinations.
It runs well enough in Windows Subsystem for Android!
I'm surprised not to see https://cryptpad.fr/ here, a FOSS, self-hostable E2EE web based office suite. Not as feature rich as GDocs but offers the basics in a more secure manner.
While Chromium itself is a very solid platform, and correspondingly Chrome is a hard exploitation target, it's quite easy to screw up a fork of it. Comodo Secure Browser was a chromium fork that was fixed to an old version of the renderer with known security issues and was built to disable the sandbox. It also added libraries that were compiled without ASLR that worsened security for every application that loaded them.
Chrome has an enormous security team behind it in addition to P0, so bounties on Chrome exploits are around $500k. FF bounties are a fifth of that, which is probably a portion of less security, and a portion of lower target market. Brave could be doing terrible things that without an audit would be unknown. Web3 code is pretty terrible on the whole, so adding that to a secure base may not be great...
The Intel ones are quite a bit easier, but still not as easy as a PC. You need to disable some FW security settings to allow for a non Apple kernel to boot.