open-pwa standart

Trying to generate a standardt for browser like server deployments

• Web Worker API
• Minimim Browser API
• Browser Addon that allows Native installs as also handels post message routing (native messaging api)

Breaking NEWS

• 11.02.2022 - Open PWA Gets less Focus as the new Focus is on @internet-of-presence/IoP A Total new Internet 4.0
• 30.07.2021 - http://webcache.googleusercontent.com/search?q=cache:https://blog.logrocket.com/why-use-electron-alternative/&strip=1&vwsrc=0
• 19.05.2021 - Google starts pwa Protocol Handler Registration support.
• 20.09.2020 - Epic Games has started war on Apple to open the ecosystem even more wide while we can already. With OpenPwa that is not even needed as you get the ability to run your code on iOS Already.

OPEN-PWA Platform turns any device into a Cloud!

Get Reach and Power with your Hybrid Apps on any Device and Scale! A Universal Entire Operating System Platform Interface and Framework!

We see at present the trend of other Projects to move in our direction i like it :) Lets Mentoin them

• Crossplane
• oam.dev
• kubernetes.

Open Pwa is a Platform that runs on Any Device with a easy installer and then allows you to run WebSites and Applications with Nativ Capabilitys. It has a Permission System, Window,Task, Prozess Manager, Install & Update Api Inspired by ServiceWorker Concepts.

It can change everything as a Open Platform to port your existing software or create new Software with the most Efficent Open Source Frameworks around.

It Also Offers its own Formart for Cloud Deployments any device can be part of any cloud or its own cloud. Platform by providing the needed API's to legacy Platforms a dropin replacement for the electron framework that scales more well when multiple applications get executed on the same host. It offers a Total new way of Deployment and Application update concepts.

Free Open Source P2P Community Foundation owned!

While i am at present the only one working here it is intended to move this Later to a Open PWA Foundation and maybe partial Apache and OpenJs we can not transfer this complet to them as they do not fully complai with our Ethics of fast forward Development This Project has a Complex Mindset behind it. While i think every one will love and use this

Downloads

Open PWA ships as self containing installer that then switches to its own package management system so you do not need to handle updates yourself while the installer supports a "no-update" option in that case you can handle updates how you like it even via a own open-pwa-

Download the right installer for your OS

v0.55.0: (Aug 1, 2021, based off of Node.js v16.4.2, Chromium 92.0.4515.107) : release notes NOTE You might want the SDK build. Please read the release notes.

Linux: 32bit / 64bit

Windows: 32bit / 64bit

Mac 10.10+: 64bit

Use "Legacy build" for Win XP and early OSX.

latest nightly build from git tip: https://github.com/open-pwa/live-build/releases

Android: use the Android Store or git clone this repo and follow the android build instructions

iOS: use the ios store or git clone this repo and follow the iOS build instructions

How does it WORK?

Open Pwa is a Platform build with the @stealify/stealify Framework the EE Encapsulation Standard Open PWA also offers some high level tooling also build with stealify to package and deploy your code via vmpack and vmdeploy (deployless).

https://oam.dev/

An App-centric Model

1. Application first - the platform is built around a self-contained app model, where operational characteristics are also part of app definition, free of infrastructure here.
2. Clarity and extensibility - an open standard to modularize your platform capabilities into reusable pieces, with freedom to bring your own abstractions and implementations.
3. Runtime agnostic - a consistent experience to deploy and operate your apps across on-prem clusters, cloud providers or even edge devices.

Information for Google Carlo Users

As Google Carlo is deprecated we will offer @open-pwa/carlo with the same and more abilitys which will get maintained as it is a shared dependency of open-pwa that can run standalone simply use npm i @open-pwa/carlo inside open-pwa/packages/carlo you can find readme.md and additional explainations.

We Are more then happy to announce that we will keep that functionality running and will reuse it as Carlo is not maintained anymore we adopted it's code and made a ECMAScript 6+ version out of it to keep maintance overhead low. We will publish that under @open-pwa/carlo@>0.10.0

Open PWA Compared with WebView2, Electron, NW.JS and so on

• Electron apps More Efficent and allows to run them directly on open-pwa without a indipendent electron installation. Adds Open Pwa Features!
• WebView2 Allows Hybrid Apps while OPEN-PWA is a Hybrid App Platform it allows to turn Hybrid Apps and even Websites Into Nativ Apps!
• HashiCorp Terraform Compatible Syntax Support! Enables Remote Deployments of Terraform Specs. (You can Deploy from and to terraform)

There is a discussion in https://news.ycombinator.com/item?id=18355345 which shows that Open-PWA is still the way to go as it manages the Runtime or serverside dependency while chrome manages updates it self.

Current Implementation

• Stealify + https://github.com/amino-os/Amino.Run

Evaluation

• https://github.com/amino-os/Amino.Run
• IREE (Like WASM) https://github.com/google/iree
• electron
• unraid
• open-stack
• kubernetes
• docker
• nodejs (Including Java InterOp via node-graalvm)
• os nativ apps
• cordova-nodejs-mobile
• wasmer
• weex
• QT
• wxWidgets
• deno
• cordova

Permissions - Application based Permissions on the Host

Service Workers - as Deployment Package

We Will Deploy the serviceWorkers in 2 Formarts WASM using the WASI and JavaScript using the JS API OpenPwa gets called with a serviceWorker URL

Run a PWA on a None Browser based Runtime

We can expect a RasPI with a small lcd screen to display a scrolling text without a browser.

• using sharedModules as formart Comes into mind but not sure.

Remote API Polyfills for wasm

Local WASM needs to talk to OpenPwa it can do that via the JS Api or we Supply a WASI Shim

• wasi
  • Run wasm in a browser client with access to a remote resource as would it be the local environment.
• chrome
  • run a uwasi remote host and expose that as the current browser to JS

This will make service worker driven pwa and pssa work.

PSSA - Progressive Server Side Applications

they will get deployed via installation of a remote serviceworker.

What and Why?

We will research and create an environment agnostic way to run PWA's in browsers and none browser environments that do not support PWA's. we will offer a permission-based API and implement all the functionality that chrome offers for a PWA and all NativSystemCaps.

so this will be a single daemon or app or server it is not so important how we name that. It will expose API's that a remote website can call to request a local installation and use of existing Platform features.

The Implementation will be written in JS using GraalVM with Stealify to get it even more embedded able while keeping the code understandable by all ECMAScript knowing people,

Concepts open-pwa runtime

• open-pwa indipendent collection of packages that run on all platforms or the single platform they represent

  • service-manager (Is the Main Entrypoint for the open-pwa-manager)
  • permissions
  • serviceWorker-api The main installer api for open-pwa-apps
  • buildscripts for open-pwa-installers

• cordova-plugin-webserver

• cordova-platform-open-pwa inhires cordova as we are compatible

• open-pwa runtime runs on a remote host or the local desktop pc look into amino.run

• It offers a service worker deployment interface open-pwa://my-app-id and ://open-pwa/my-app-id that exposes *.

  • additional on ip:port for restricted deployments without access to dns or host protocol services.
    • grpc endpoint
    • http2 endpoint
    • websockets endpoint

• It offers all browser related API's for PWA's like storage and others

• Custom kublet implementation done via rust

• First Implamentations JS+WASM

  • ECMAScript 6+ Modules Compatible for NodeJS (mobile) (graalvm) Based Host Platform
    • upwa rust + wasmer + deno
    • uwasi offers wasmer-js Platform bindings.
    • graalvm and also node-graalvm https://github.com/lazar-mitrovic/GraalREPL + es-permissions can be used for the first implamentation

• API's

  • run worker process
  • register desktop app
  • listen on address device
  • systeminfo
  • user management (maybe reffered to the underlaying os not sure if we should implement it)

What will Open-PWA Solve?

It will provide a ecosystem for a total new concept to deploy existing PWA's to diffrent Platforms then the Browser as also New Concepts for Live Updates and Deployments PSSA - Progressive Server Side Applications maybe it will be called PSSS - Progressive Server Side Services. of existing Applications Running. This is research on the new Container Caps of wasm also.

• permission system isolated access to device caps
• running processes on the device with access to os api's via unified api
• universal install system
• universal software update system
• supports GraalVM, docker, kubernetes, open-stack, chrome

Collaboration

Simply contact me via the issue section at present it is fast to get into the project as it is quit new :)

History

This is an Open Source Effort it got initialized by Frank Lemanschik not on purpose because he has written that article https://medium.com/@frank_lemanschik/is-it-all-about-the-package-manager-43077634124c?sk=1fdba664c3fdce60b3a5d4d10d0e8773

It Joins with a lot of my other projects that i was working on the last 20 years

• direktspeed server
• direktspeed os
• direktspeed serverless *
• serverless *
• stealify
• Maybe 1000+ Projects

Into one giant open project OPEN-PWA That will hopefully deliver Expirences better then ever to the user. And also make Developers More Efficent and Happy.

PREREQUISITES Windows, Linux, macOS, Android Dev Only, iOS Dev Only

bash, git, mv, rm, tr, type, curl/wget, base64, sudo (if not root), make (GNU) tar (or unzip on OSX and Windows), gpg (optional verification)

Package Manager for the OS

• brew (macos)
• chocolatey (windows)
• apt (bash)(linux)

Development Linux

Use existing n and pm2 installs maybe create a seperated user profile for testing

for packaging use -a arm64 or x64 all the nodejs build flavors by default matching current platform.

# Fresh install
curl -sL https://git.io/open-pwa-install | OPEN_PWA_HOME=~/.open-pwa bash -s -- -y -n

## Link existing installs  
mkdir ~/.open-pwa
ln -s ~/n ~/.open-pwa
ln -s ~/.pm2 ~/.open-pwa

OpenPWA's relation to deployless

OpenPWA is the foundation of @direktspeed/deployless it uses open-pwa under the hood.

Diffrences between GUI App Methods

• using own versions
  • Electron uses a own nodejs version bundled with lib chrome both are older both are patched
  • nwjs uses always the newst nodejs + chrome and is a chrome app that glues libnode.so together.
• use the systems version
  • carlo using pupeteer
  • playwright using the chrome dev protocol.
• WiP! Experimental Research graalvm
  • glueon and smilar projects. allows interaction via libnode-graal.so later.

Missing parts

Shortcut and Protocol DNS management. while we could intercept that maybe on sandbox level? Inside the app?

Supported Package Formarts

• serviceWorker
  • appimage
  • docker
  • tar.gz
  • git

Commercial Offer

If you have BOYD Bring your own device enrolled in your company you can install our Enterpise versions via your Local iOS Deployment and management Servers and or Android / Fuchsia Deployment servers.

We Can help you to streamline your development process. Simply leave us a message.

Run

open-pwa run "pathOrUrl/serviceworker.js"

serviceWorker.js

export const registerServiceWorker = {
  ...hooks
}