HOW WE TESTED…
To begin with, we made sure that all typical installation scenarios were well covered by visiting the respective project web pages and searching repositories such as Flathub and Snap. We installed the corresponding Android app for each of the browsers on a mobile phone for testing.
When not deliberately exploring the features of each browser, we spent time with each of them in an informal context, using them for typical day-to-day surfing. This meant signing into online accounts, importing bookmarks and genuinely using each one for some everyday work, such as creating this article using Google Docs, and tasks such as responding to emails.
As four of the five browsers use the same rendering engine, we didn’t notice much difference in actual web page rendering. The outlier with its own engine, Firefox, is adherent to the same web standards as the Chromium engine. So, once again, it didn’t perform noticeably differently in the business of actually rendering the pages.
HOW WE TESTED…
To begin with, we made sure that all typical installation scenarios were well covered by visiting the respective project web pages and searching repositories such as Flathub and Snap. We installed the corresponding Android app for each of the browsers on a mobile phone for testing.
When not deliberately exploring the features of each browser, we spent time with each of them in an informal context, using them for typical day-to-day surfing. This meant signing into online accounts, importing bookmarks and genuinely using each one for some everyday work, such as creating this article using Google Docs, and tasks such as responding to emails.
As four of the five browsers use the same rendering engine, we didn’t notice much difference in actual web page rendering. The outlier with its own engine, Firefox, is adherent to the same web standards as the Chromium engine. So, once again, it didn’t perform noticeably differently in the business of actually rendering the pages.