| OLD | NEW |
| (Empty) | |
| 1 WebAPKs are a proposal to improve homescreen shortcuts by: |
| 2 - Giving them a spot in the app launcher |
| 3 - Enabling web pages to open a WebAPK when a user taps on a URL which belongs to |
| 4 a WebAPK |
| 5 - Improving resource and permission attribution |
| 6 |
| 7 In short, they attempt to providing additional glue to give Progress Web Apps |
| 8 deeper integration into the Android OS, similar to native apps. |
| 9 |
| 10 The directory is broken down as follows: |
| 11 - shell_apk/ - a template APK which can be customized for a given domain based |
| 12 on its Web App Manifest: https://www.w3.org/TR/appmanifest/ |
| 13 - libs/client/ - a client library meant for a host browser to interact with |
| 14 WebAPKs |
| 15 - libs/common/ - common library used by the WebAPK and host browser |
| 16 - libs/runtime_library/ - a library which can be dynamically loaded by a |
| 17 ShellAPK. A host browser provides the library which the ShellAPK uses to |
| 18 implement the majority of its functionaly. For chrome, this library is |
| 19 packaged into Chrome's assets file and extracted as needed. This approach |
| 20 ensures that the majority of the WebAPK logic is shared and can be updated |
| 21 as often as the host browser, without the need for updating each individual |
| 22 WebAPK. |
| OLD | NEW |