I think one big problem with this approach is that if the people behind this find a niche good enough its very easy for browsers to just implement the new ideas and completely kill the competition giving everyone has a deployed browser already.
Im doing something that is based on browsers for instance, but the end product diverge quite a bit from traditional browsers and if they try to play the catchup game, i have at least a 2-year window of opportunity.
Remember PhantomJS? And Phantom was actually providing something browsers were not doing at the time.
It has no real distinct features from what browsers already do right now, and whatever way they make it easy to use, if the product by some change get traction, it will be easy for them to just ship with that feature built it.
It may provide some value on convenience, but its easily copiable by a competitor that is deployed everywhere, which is a big threat to their bussiness model.
Dropbox offered far more than just convenience. And at least it was something new.
This on the other side has very very slim novelity and convenience. And tools like this exists since at least a decade and never really took off. Maybe for a reason?
> This is trying to sell the concept of a chrome-less browser-window ("install as app"), a feature your browser already has.
As a dev, service workers are a PITA and getting them to work with with our products is a bit of a hit and miss. Installable / pinnable web apps are only available if the original web dev has made them available. Web catalog and electron wrappers are for people who want to wrap apps and sites that are not nor ally available.
Sometimes convenience can be enough.