Welcome to Chrome Beta for Android
• Preview the latest features: Try out the newest features. (Sometimes these may be a little rough around the edges.)
• Give early feedback: Let us know what you think and help make Chrome for Android a better browser.
You can install Chrome Beta alongside your current version of Chrome for Android.
Along with the stable version of Chrome Browser, there are tons of other distribution channels that let you try out the newest versions before anyone else. Chrome Beta is the first step before fully launching a new version, offering unique features that only arrive to later versions when they arrive for mass distribution among all users.
While this version of Chrome Dev is usually at least two versions ahead of the stable channel (as indicated by its serial number) Beta is just a step before them which is why it’s already stable enough even for use as a main browser tool. Notwithstanding, its main objective is to work as a trial zone for users to send feedback directly to developers.
The best thing about Chrome Beta is that it works side-by-side with the completely stable version of the well known browser, without interfering at all and with each running independently. Ultimately, Chrome Beta is another awesome way to enjoy the latest improvements on Google’s browser in a controlled and safe way.
Google Chrome Beta is a beta version of the popular Chrome web browser. Available for download on Microsoft Windows computers, Google Chrome Beta lets users test various new features before officially being released.
It also lets them send feedback about any bugs or limitations they encounter. The beta version of Chrome is free to download and can be used alongside the stable version.
What is new in Chrome beta?
- Developers can restrict the types of plugins to load as ‘<embed>’ or ‘<object>’ HTML elements. This allows developers to block Flash in their pages.
- It removes support for non-standard RTP data channels and encourages the use of SCTP-based data channels.
- Chrome will return nothing for navigator plugins and mine types previously used for Flash.
- Establish a policy for removing APIs and giving developers enough time to make changes to keep their sites running. This is announce through a mailing list and through warnings and time scales in DevTools Console. Chrome developers then wait, watch, and remove the feature when usage drops.