Google Chrome Browser's version 72 stable and version 73 beta for Android got released recently. The stable build and the beta one each bring something new to the table, so without further ado, let's proceed with our feature breakdown all courtesy of XDA Developers, Android Police and 9to5Google.
Trusted Web Activities
The stable channel for Chrome got updated to version 72 and it finally does allow app developers to publish their Progressive Web Apps on the Google Play Store. All of this is thanks to Google announcing their 'Trusted Web Activities' software. TWAs differ from normal websites and Chrome Custom Tabs by the simple fact that they run in full-screen and do not have a browser UI. They also get special features such as support for push notifications, background sync and form autofill. On the other hand, the "trusted" moniker means that Google runs extensive checks whether those PWAs can be trusted and are from the same developer as their website counterparts. This should make things easier for developers to publish "standalone" web apps for Android, directly installable from the Play Store and buildable without involving too much effort.
Google have begun testing dark mode for Chrome for Android in version 73 beta and so far it looks promising. This has come quite late if we have to compare to when they have started working on the same dark mode implementation for Windows and macOS.
To enable the experimental dark mode in Chrome Beta, you will have to set the 'Night mode' option to 'Always on' inside your Android Pie-running device's Developer Options menu. Currently, there are many hardly legible UI elements due to this being still a work-in-progress, so be cautious.
A commit on the Chromium Gerrit has been spotted by Chrome Story, which indicates a new performance-enhancing feature coming to Chrome. It has been submitted last October, has got some newer submissions last week and has been described as "an experimental browsing mode that restricts resource loading and runtime processing to deliver a consistently fast experience," but at the expense of silently breaking some content. It is still not merged, indicating that it requires further work to be done. Looking at Google Chrome's dominance in the Internet browser space, this may not be a good solution to this still unresolved problem by breaking other stuff. Let's wait and see how things develop in the future.
Those were three of the hottest news about Chrome for Android. Stay tuned to TestingCatalog for more Android app-related news and reports.
Are you looking for more insights? Check our daily Community Reports on TestingCatalog.