It’s a shame that I haven’t collected many of the Chromium code commits that I could have listed here to explain why I am saying this. Lately, I keep seeing more features showing up on Chrome and Chrome OS from the Android land.
Anyways, I decided to write this one up mainly because of this piece of information that François Beaufort shared today. The Chromium team is working on a project (reminds me of project butter and other projects that the Android team has done) named Fizz. Its aim is to make web apps (read Chrome apps) more powerful.
Fizz is an exciting new effort by the chromium team aimed at making web applications first-class citizens on mobile by giving developers more powerful and safe capabilities to the web platform:
– Service Workers¹ provide a way for applications to reliably “go offline”.
– Push API² used by application servers to send messages to web apps, whether or not the app is active in a browser window.
– Network Information API³ to access the underlying connection information of the device.
– Geofencing API⁴ makes it possible to be notified when a device enters or leaves specific regions.
A wake lock is a mechanism to indicate that your application needs to have the device stay on.
Any application using a WakeLock must request the android.permission.WAKE_LOCK permission in an <uses-permission> element of the application’s manifest. Obtain a wake lock by calling newWakeLock(int, String).
As far as I know, Mozilla is also going the same route, a little more faster. Google wants to grow their web apps baby and continue to depend on native apps until the scene is fully set.
What do you guys think?