Registration Project
Another important point to note is that the Origin Trials Framework (implemented in Chrome) enables manufacturers to expose and test hardware (or software) capabilities without having to go through the standardization process. For example, a phone maker could expose an API for reading the values of a pressure sensor, refine it, then submit it for consideration to the W3C.
Anyway, access to hardware features are only a subset of what makes a great app. There are also software features traditionally employed by native apps that are now available to web apps.
Traditionally native features that PWAs can also use
push notifications
working offline
adding an icon to the home screen
being installed into Android (i.e. in the apps drawer and in Settings)
receiving intents
triggering the native Android share dialog
launching in full-screen
clipboard access
persistent auto-login using the Credentials Manager API
hardware-accelerated 2D/3D graphics using CSS3, HTML5 Canvas or WebGL — check some of theHTML5 Canvas demos, WebGL sites or the three.js library. Game engine performance in WebGL is close to native.
accessing the filesystem (Chrome and Opera) and reading user-selected files in any browser
really slick, smooth UIs with 60fps animations
These features cover a lot of use cases, and many popular native apps nowadays could be rewritten as PWAs. Take Slack, for example. Its open source alternative, Rocket.Chat, is building a PWA version. For more PWA demos, see https://pwa.rocks.
While PWA capabilities are rapidly evolving, there are still somethings you can’t do yet.
Native features coming to PWAs
handling intents — being the share target, e.g. a PWA chat app that receives an image to set as the user’s avatar
Native Android features that PWAs currently lack
contacts, calendar and browser bookmarks access (though lack of access to these could be viewed as a feature by privacy-conscious users)
alarms
telephony features — intercept SMSes or calls, send SMS/MMS, get the user’s phone number, read voice mail, make phone calls without the Dialer dialog
low-level access to some hardware features and sensors: flashlight, atmospheric pressure sensor
system access: task management, modifying system settings, logs
registering to handle custom URL schemes and protocol, or file types
For most use cases, PWAs can do the job and also be a much better investment — you don’t have to develop and maintain three separate code bases for Android, iOS and web. PWAs also have certain features that native apps lack.
Progressive Web App advantages over native apps
low friction of distribution — if your progressive web app is online, it’s already accessible for Android (and other mobile) users. 65.5% of US smartphone users don’t download any new apps each month. PWAs eliminate the need to go to the app store, search for the app, click Install, wait for the download, then open the app (until Android Instant Apps launch). Each of these steps loses 20% of the potential users.
Anyway, access to hardware features are only a subset of what makes a great app. There are also software features traditionally employed by native apps that are now available to web apps.
Traditionally native features that PWAs can also use
push notifications
working offline
adding an icon to the home screen
being installed into Android (i.e. in the apps drawer and in Settings)
receiving intents
triggering the native Android share dialog
launching in full-screen
clipboard access
persistent auto-login using the Credentials Manager API
hardware-accelerated 2D/3D graphics using CSS3, HTML5 Canvas or WebGL — check some of theHTML5 Canvas demos, WebGL sites or the three.js library. Game engine performance in WebGL is close to native.
accessing the filesystem (Chrome and Opera) and reading user-selected files in any browser
really slick, smooth UIs with 60fps animations
These features cover a lot of use cases, and many popular native apps nowadays could be rewritten as PWAs. Take Slack, for example. Its open source alternative, Rocket.Chat, is building a PWA version. For more PWA demos, see https://pwa.rocks.
While PWA capabilities are rapidly evolving, there are still somethings you can’t do yet.
Native features coming to PWAs
handling intents — being the share target, e.g. a PWA chat app that receives an image to set as the user’s avatar
Native Android features that PWAs currently lack
contacts, calendar and browser bookmarks access (though lack of access to these could be viewed as a feature by privacy-conscious users)
alarms
telephony features — intercept SMSes or calls, send SMS/MMS, get the user’s phone number, read voice mail, make phone calls without the Dialer dialog
low-level access to some hardware features and sensors: flashlight, atmospheric pressure sensor
system access: task management, modifying system settings, logs
registering to handle custom URL schemes and protocol, or file types
For most use cases, PWAs can do the job and also be a much better investment — you don’t have to develop and maintain three separate code bases for Android, iOS and web. PWAs also have certain features that native apps lack.
Progressive Web App advantages over native apps
low friction of distribution — if your progressive web app is online, it’s already accessible for Android (and other mobile) users. 65.5% of US smartphone users don’t download any new apps each month. PWAs eliminate the need to go to the app store, search for the app, click Install, wait for the download, then open the app (until Android Instant Apps launch). Each of these steps loses 20% of the potential users.
Komentar
Posting Komentar