- From: RichardNeill <notifications@github.com>
- Date: Mon, 19 Jul 2021 13:42:49 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 19 July 2021 20:43:01 UTC
That proposal is useful, but it does the converse of what I am trying to achieve... I actually want to expose different subdirectories of the same domain, as if they were independent apps. For example, we have "an issue tracking app" and a "brainstorming app" and a "kpi tracking app" - these are all actually the same codebase, running the same backend, on the same server, on the same domain - differing only in the subdirectory of the landing page. But I want the user experience to be "Click the KPI icon on your phone, if you want the KPI app". In our use-case, the server should only know which app it's serving based on the query-string (ideally not even a subdirectory). [Aside: we also don't really care about the service-worker - it's a no-op, whose only purpose is to exist sufficiently to allow the user to receive "install this app" prompts, get an icon on their desktop, and then have the "app" launch the web-browser fullscreen, without the url-bar visible.] -- 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/449#issuecomment-882845890
Received on Monday, 19 July 2021 20:43:01 UTC