Idea No. 3: PWA-Centric OS
If PWAs are good enough apps for most consumers, and if some PWAs can be approved access to specific hardware functions and APIs, a PWA-centric OS can be the next universal OS for consumers. Sounds good? Read on...
Imagine an OS almost at its bare minimum, that removes the visible browser container and make the OS run PWAs as if they are native. This OS should make PWAs first class citizens. In fact, it requires apps to be PWAs in order to run in the OS -- except for the browser/PWA engine which should be native. Even the OS's native apps can be PWAs as well, including device configuration, management and settings features.
This OS could require 3rd party browser makers to create engines that can replace the OS's default browser/PWA engine. Thus, the OS can be easily re-branded just by simply replacing the default browser/PWA engine.
Until new standards are created for PWAs to get specific hardware access, the OS can fill the need with built-in APIs combined with special review and approval processes. For these kinds of PWAs, they are written specially for the OS. The best way to break them free is for the specific hardware to PWA standards to be created.
Although Chrome OS was close to this, it was not, and still not, PWA-centric. A PWA-centric OS can be made smaller and more compact. It can be ecosystem-free as well -- except for the special PWAs that should get approved hardware API access. PWAs can open up new marketplaces for PWAs. Although PWAs are OS-transparent, a PWA-centric OS that puts PWAs first class can be the best OS to run PWAs on.
I wonder if Google's Fuschia OS project can be a candidate? Regardless, whoever makes a PWA-centric OS can be the first to break the store ecosystem trend. With PWAs, there can be no need to get tied to a store's ecosystem, that's also tied to an OS. A PWA-centric OS will make computing more open and free... again.
Imagine an OS almost at its bare minimum, that removes the visible browser container and make the OS run PWAs as if they are native. This OS should make PWAs first class citizens. In fact, it requires apps to be PWAs in order to run in the OS -- except for the browser/PWA engine which should be native. Even the OS's native apps can be PWAs as well, including device configuration, management and settings features.
This OS could require 3rd party browser makers to create engines that can replace the OS's default browser/PWA engine. Thus, the OS can be easily re-branded just by simply replacing the default browser/PWA engine.
Until new standards are created for PWAs to get specific hardware access, the OS can fill the need with built-in APIs combined with special review and approval processes. For these kinds of PWAs, they are written specially for the OS. The best way to break them free is for the specific hardware to PWA standards to be created.
Although Chrome OS was close to this, it was not, and still not, PWA-centric. A PWA-centric OS can be made smaller and more compact. It can be ecosystem-free as well -- except for the special PWAs that should get approved hardware API access. PWAs can open up new marketplaces for PWAs. Although PWAs are OS-transparent, a PWA-centric OS that puts PWAs first class can be the best OS to run PWAs on.
I wonder if Google's Fuschia OS project can be a candidate? Regardless, whoever makes a PWA-centric OS can be the first to break the store ecosystem trend. With PWAs, there can be no need to get tied to a store's ecosystem, that's also tied to an OS. A PWA-centric OS will make computing more open and free... again.
Comments
Post a Comment