-
-
Notifications
You must be signed in to change notification settings - Fork 813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PWA support for OS.js applications and framework #801
Comments
There's been a couple of discussions around stuff like this on Gitter etc. but never really went anywhere. I'm not really sure if there's much gain in making OS.js interface itself PWA, but having direct support for launching bundles etc. would indeed be nice. |
I think an offline capable web-based application platform is powerful. PWA is perhaps a start, but would not rule out native clients for iOS/Android/Desktop if the need be. This would be particularly interesting if OS.js were to leverage the wasmer ecosystem to enable offline-first connected application delivery for a true-blue web-based operating system. Perhaps even a self-hosting web operating system based on emception some day? |
Ah, yes. This skipped my mind :) |
With |
great idea, re 'navigator.keyboard.lock(), osjs could use more keybindings.' |
I'm probably going to use mousetrap to implement a bunch of shortcuts on my fork in the near future, I'll try to bleed them over to the main OS.js whenever possible. |
this would require
ideally, preserve the app state like figwheel |
By doing so, OS.js application packaging would align with PWA standards and WebPack support. This further paves a path to OS.js support for Web Package and Web Bundles which builds on this appmanifest standard.
In a nutshell, it would undoubtedly be a a great roadmap item for OS.js to evolve into an execution environment for bundled web applications. This includes both:
The text was updated successfully, but these errors were encountered: