- From: prime2358 <notifications@github.com>
- Date: Thu, 31 Aug 2023 04:58:17 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/1096/1700901687@github.com>
I will definitely come back after reading the spec, but until then I would suggest to take a step back and think about basic questions like: What is a website, what is a web app, do we have a supported definition (by most people at Apple, Google, Microsoft, Linux, Chrome, Safari, Firefox, Brave etc. who care about web applications)? I mean the main process that happens is called in this spec web app -> installed web app, still Apple is refusing to use this word and interestingely, I am with them in this one. It is very bad that the very things the standard describes is refused by a big player, and even chat-gpt says it is confusing since no installation happens :) It may seem a big thing or a big re-write but actually one could do this on a weekend. Of course with discussions some weeks/months. It is a very basic, fundamental thing this distiction of websites and web apps (or currently web apps and installed web apps but I really find it confusing on many levels). I mean Apple wipes website storage, all of it, without user consent, after some 7 day rule. Not by web apps (or installed web apps or after added to home screen). There are big legal disputes, even Tim Cook says there is no problem, web apps can do anything on Apple platforms like native apps. And what is the legal source, what can be the legal source of the definition of a web app? This standard. Big responsibility. Very important. It is worth thinking about basic things over and over when something is that important. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1096#issuecomment-1700901687 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1096/1700901687@github.com>
Received on Thursday, 31 August 2023 11:58:23 UTC