As more companies and independent developers move to Progressive Web Apps as their preferred solution for their own applications, Microsoft and Google are slowly adding new PWA features to improve the performance of Windows web applications and other platforms.
For those who are not aware, the Progressive web app or PWA is the latest web technology that allows anyone to use websites as local mobile or desktop applications.
In recent efforts to improve hands-on web applications, Google appears to be working on a new API that will allow Chrome Progressive Web Applications (PWAs) to “process”
In a browser, the file handler represents the ability of a web application to process a file with one of a set of MIME types and / or file extensions. For example, when you install an image editor as a web application, it may register its ability to process one of these file types (jpg, png, etc.) in its manifest.
Of course, you will expect the web application to open image files in one of these formats when you double-tap images stored on the system (offline). Although the web application may register its ability to process one of these file types in its manifest, this feature is not currently supported by Chromium.
In the documentation, Google notes that the goal of their new project is to improve transparency between web applications and native applications and to provide a “more consistent user experience” by enabling support for processing files.
As part of the next update to the web application, Google is working on a new permission line that will ask users to confirm whether PWA can be registered as a processing file for certain file extensions.
To enable this feature, Google runs a file processing API:
“Different translation strings exist for each possible number of manipulators to allow better translation between languages with different sentence structures. File manipulator information is extracted from WebAppRegistrar (instead of the flashing manifest) to match what is registered in the operating system.
Chromium already has support for origin testing in Chrome and other browsers, but the new file processing APIs are different from other APIs that go through the origin testing process because they enable and deactivate test results in some states that change in the operating system (register processing files).
“This means that the trial version of the original requires some special architecture: Every time you visit a web application, we check if there is a valid trial tag and, if so, register the processing files and save the token expiration time. If the tag is not valid, we write off the file handlers. When we start Chrome, we also disable file handlers for all applications where their exit test tag has expired, ”said Google.
Google is currently experimenting with the feature in Chrome’s Canary builds and is expected to launch later this year.