Chrome's enhanced Web apps, known as Packaged Apps, take on more features to compete with native mobile apps, including in-app payments. Google's Identity API will let developers give more control to their users. (Credit: Google) The foundation for making Web apps as powerful as native code slowly slides into place as Google announces new backend support for its Chrome Packaged Apps in a Chrome dev update on Monday. Related stories: Rival mobile browsers chip away at Safari's lead Google gooses Chrome with network speed-boost idea: 'QUIC' Google Now comes closer to Chrome, shares TV show info Google's Chromebook photo app tries to pick your best pics Google sharpens ax for Chrome Frame The new support, expected in the stable version of Chrome in around six weeks, allows Packaged Apps to use a new set of Application Programming Interfaces (APIs). Packaged Apps are a variant of Web sites, like Gmail, that are designed to load flawlessly even when not connected to the Internet. These include the In App Payments API that's built on Google Wallet; the Identity API for authentication; the Native Messaging API so that Chrome apps can communicate with native apps; a Media Gallery API for accessing locally-stored music, image, and video files, including from iTunes; a Bluetooth 4.0-based API that Google says will let the Web apps connect to Low Energy health-tracking devices; and an Analytics API for monitoring app user data. Some of the additional features will provide developers with more feature-rich options that native apps have been able to lord over the Web. In the In App Payments API, for example, Google notes that developers will be able to build simple one-time and subscription-based billing into their Web apps. The Identity API will let developers provide more granular control over how much information about user behavior in an app becomes available to the public. It's small improvements like these that Google and other browser developers hope will continue to keep developers interested in coding for the Web, as well as making Chrome a bit more like Android. But keep those dreams of Chrome and Android merging in check -- that's still years away.
Chrome's enhanced Web apps, known as Packaged Apps, take on more features to compete with native mobile apps, including in-app payments.
Google's Identity API will let developers give more control to their users.
(Credit: Google)
The foundation for making Web apps as powerful as native code slowly slides into place as Google announces new backend support for its Chrome Packaged Apps in a Chrome dev update on Monday.
Related stories:
- Rival mobile browsers chip away at Safari's lead
- Google gooses Chrome with network speed-boost idea: 'QUIC'
- Google Now comes closer to Chrome, shares TV show info
- Google's Chromebook photo app tries to pick your best pics
- Google sharpens ax for Chrome Frame
The new support, expected in the stable version of Chrome in around six weeks, allows Packaged Apps to use a new set of Application Programming Interfaces (APIs). Packaged Apps are a variant of Web sites, like Gmail, that are designed to load flawlessly even when not connected to the Internet.
These include the In App Payments API that's built on Google Wallet; the Identity API for authentication; the Native Messaging API so that Chrome apps can communicate with native apps; a Media Gallery API for accessing locally-stored music, image, and video files, including from iTunes; a Bluetooth 4.0-based API that Google says will let the Web apps connect to Low Energy health-tracking devices; and an Analytics API for monitoring app user data.
Some of the additional features will provide developers with more feature-rich options that native apps have been able to lord over the Web. In the In App Payments API, for example, Google notes that developers will be able to build simple one-time and subscription-based billing into their Web apps. The Identity API will let developers provide more granular control over how much information about user behavior in an app becomes available to the public.
It's small improvements like these that Google and other browser developers hope will continue to keep developers interested in coding for the Web, as well as making Chrome a bit more like Android. But keep those dreams of Chrome and Android merging in check -- that's still years away.
