Re: [w3c/manifest] suggest in standard calling website->webapp process unified "add to home screen" or such in all browsers (not install) (Issue #1096)

Some legal aspects.
Web apps are an alternative to native apps, the web is a competitive distribution platform.
The European DMA law will force apple to accept any browser engines on the platform, Chromium too.
So if Chromium/Google/Apple etc. people got everything right (I beleieve it is how I think but it must not be, right means that web apps can flourish) it would be a half victory (full screen, total headless, drag domain to home screen, call it add to home screen or on desktop drag to desktop, on mobile drag to home screen...)

Still first we might debate first what is right for Chromium and scond there might be some OS problems from Apple/Linux folks like they know better. Linux gives an irritating arrow to the icon, Apple might not let just drop something from chrome to their sacred home screen but force people find add to home screen.

Such directives can only be made from web standard communities like the domain should be draggable to home screen because it is a very unified and clear way for the users to do what they want: make a web app from the website to use it like a native app: from launchers and full screen without browser overhead.

And then there is some unified thinking and Linux people will just read the standard and learn that arrows are for shortcuts and web apps are not shortcuts to websites. I do not think Linux people have anything against web apps they just dont really care that much and the communication is not clear, even in this standard it is confusing that it may be an option that a web app wants to run in a browser...

In the end nothing is a web app, it is ok I think that offline is not a core thing anymore (or is it on some platforms?) but as of now  with no clear idea a web app is a website that has a shortcut, or not really more.

Totally frustrating.
If there is no clear path, we will never arrive.
And legally enforcable will be nothing!
On all platforms it will be different, there will be no clear concept in a normal user.

Is there is web app folks actually?
And yes, a concept should be communicated in this standard.
The offline and caching is not core part, the service worker is fantastic capability, everybody should use it.
But a website can also work offline.

One small step for a web app to get out of the browser still it is sooo poorly done!

















-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1096#issuecomment-1700763097
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1096/1700763097@github.com>