Android Police

Articles Tagged:

chrome dev summit


Chrome Dev 48 Rolls Out With Early Bluetooth Web API Support On Chrome OS Dev Channel And Android Marshmallow

Google's Chrome development team regularly implements new APIs to extend the possibilities for web apps to behave more like their native counterparts. The most recent addition to the Chrome dev channel allows web developers to use Bluetooth to communicate with nearby hardware. This could be used for things like an online fitness tracker that gets data from a heart rate monitor or for a controller to drive a Sphero, all without installing a native app.

These things are possible with the new Web Bluetooth API. Still in the early stages of development, this allows a web application to query for Bluetooth devices based on their capabilities, then pass messages back and forth with little or no friction.

Read More

Chrome Dev Summit Keynote Video Overviews 400 Million Mobile Chrome Users, Upcoming Browser Updates, And More

At this year's Google I/O, the search giant got to announce that 300 million people were using Chrome on a mobile device. Less than half a year later, that number has grown to 400 million. Googler Darin Fisher made the announcement at this year's Chrome Dev Summit held just before the weekend.


During the talk, Fisher touched on a number of topics, some of which we're already aware of. In Android Lollipop, WebView is unbundled from Android, allowing for easier updates and better security (along with generally making life easier for developers). Over the course of this year, Google has also removed the artificial 300ms delay that followed taps in Chrome while the browser waited to see if a second tap was on its way.

Read More

'Project Ganesh' Demoed At Chrome Dev Summit, Makes Chrome's Page Rendering A Lot Faster By Working Directly On The GPU

If you've ever used Chrome for Android, you know it can be an obnoxiously slow browser at times - especially on pages with tons of elements. Part of that, according to Google, has to do with how Chrome currently renders web content, using a pipeline that goes from the CPU to the GPU before content appears on the display. The draw commands from the web page go to the CPU, the CPU turns that code into pixels (textures), and the pixels then go to the GPU which displays them on the screen.

The CPU part of the equation is what causes slowdowns - because the process of rasterizing the page elements is very computationally expensive for even a multi-core CPU, this creates a bottleneck.

Read More