PWAs progressively behave like installed native apps on your device. And I’d like to go a little bit deeper into this one. PWAs are, in Google’s words, “user experiences that have the reach of the web.” In short, they’re web apps that can be installed on the Home Screen without having to go through Play Store or other app store. The second change – and we saw this early on in Chrome 57 beta versions – is around Progressive Web Apps. It can also be used to restrict app access. This containerized method works particularly well where you don’t want the user to have access to certain Android features that can be used to leave the app, such as the back, home, recent apps, power and volume buttons. In simple terms, apps from Play Store can now be pushed to Chrome in order to lock down devices that are used for retail displays and other types of interactive environments. The first of these is the ability for admins to install Android apps in Kiosk Mode. But it’s the Android elements that are very interesting, and I’m bringing a couple of them into the picture here. In fact, most of the changes brought to Chrome 57 – over the current Google Chrome 56 – are intended for Android as well as Chrome OS on Chromebooks. As usual, there were dozens of bug fixes from the final beta version, but the really exciting part about Chrome 57 is how Progressive Web Apps (PWAs) integrate deeply with Android. Google Chrome 57 has now been released to the stable channel, and will be available for Windows, Mac and Linux desktop users in the coming days and weeks.
0 kommentar(er)
