There are at least two major changes to the chrome application on Android M. First, chrome can distinguish between users with weak connections and users with high-speed internet connections. And then differentiate the treatment between the two. Second is about chrome permits in accessing cell phone data.
Chrome knows when you have weak connections and optimizes search results. Chrome is also slimmer and faster than before. Starting with the idea of Android One, where a stable and fast internet connection is not always possible, the new optimization of Chrome has been designed to be present for everyone.
Chrome is now aware of the power of the internet network and can modify what you see as a result. For example, if your connection is bad, you might see a colored box instead of a preview image in the search results. Optimized web pages will load four times faster and use bytes (internet data quota) 80 percent less. So even with a reduced memory usage of up to 80 MB. Chrome will also support offline mode.
The second big change is that users can see permissions on each application, and revoke them individually at any time. In line with how the application gets permission to access private data on Android M, Chrome does it too.
When you navigate to a website or application that requires permission to access the camera or data or whatever, Chrome will do what Android M does; i.e. ask the user. This will ask you in real time, right below the navigation box, whether you want to give them permission.
Based on Google's data, only about 17 percent of people say yes to Chrome's permission requests, partly because they were asked at the wrong time – or in a confusing way. But now the "yes" number is near 52 percent, maybe because Chrome is now asking permission at the right time.
Imagine you buy theater tickets, and so you visit a theater stage. Chrome might ask, "Do you want this site to send notifications?" Maybe my friend will say no, because why does theater stage need that permission? But now, because the application asks for permission when you buy tickets, it makes sense – notification permission is requested to be able to send notifications about when tickets will be available.
Chrome also allows you to take back the access rights that you have given from the permission list. Just click the icon next to the URL of the site you are visiting and you can see all the permissions that have been given on the site or application. And change them if you want it!
One of the most important parts of permissions that "handle user rejection" is the key on Android M too. User rejection is when I decide not to give an unexpected application. Say you have a mapping application and it will make things a lot easier if you tell you where you are – but maybe you are a person who is strict about privacy and hates to share location data. So you choose the no option for the permission.
A good application must still work well despite my rejection. It may not be able to provide many functions, but still must be able to work without certain permission. That's another way that Android M and Chrome are trying to fight for user authority: Both encourage developers to create applications that ask for coherent permission, and accept rejections gracefully.
Also read: Advantages of Android M