Re: [w3c/manifest] Why does this spec replicate HTML features? (#97)

@marcoscaceres I think this issue must open again for these reasons:
- If devs want to have SSR web app (server-side rendering) they must accept that nobody wants to add an app to the home screen that shows browser errors in no internet situation. Manifest is part of PWA and one key purpose is not just app work offline by old caches but works offline natively (CSR client-side rendering). To achieve this, devs must handle lots of logic like routing, ... and best way to implement these needs always start apps with specific `main.html` file in any URL and browser can cache it once for start app in any URL by that file.
- As you mention above for security reason (app introduce itself to look like another app) and browser force serve PWA apps over TLS protocol and a certificate for TLS protocol belong to a domain, not URL, a domain can't set more than one app shortcut, so we just need one main HTML file.  So for the future, we must just read the app name and icon from certificate, not from the `manifest` or `main.html` file.

And also I think register another app logic process as `service-worker` also is a huge mistake in web standard due to just register one `main.js` to start an app is enough and devs can write the logic in desired order to handle everything.

I propose this way to tell the browser that our app can be PWA (or just has CSR ability)
```html
    <meta name="display" content="standalone">
    <meta name="theme-color" content="#66ff55">
    <link rel="start" href="/?utm_source=PWA&utm_medium=shortcut">
    <link rel="main" href="/gui/main.html">
    <script type="module" src="/gui/main.js" async></script>
```
By above CSR standard propsal that indicate a `main.html` file to render all URL, we also able to write a compiler to compile web apps to native OS apps easily.
(p.s. We consider to continue this approach, not use any manifest file and make a compiler like Flutter but in HTML standards, not complete new languages.)

Last but not least as lots of good face HTML specification never get standard like [@apply](http://tabatkins.github.io/specs/css-apply-rule/) in CSS, Editors must be brave to abandoned `manifest.webmanifest` file from specification before it's too late and uses some meta and link tags.

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