#524: MiniApp Manifest
Discussions
Comment by @cynthia Jun 16, 2020 (See Github)
Before we get to a full review, why is this intentionally incompatible with Web App Manifest?
Comment by @zhangyongjing Jun 16, 2020 (See Github)
Before we get to a full review, why is this intentionally incompatible with Web App Manifest?
On the contrary, it's intended to be compatible with Web App Manifest, while focusing more on other aspects that are not covered (e.g. UI configuration, version control). Comparison is given in the Explainer.
Comment by @cynthia Jun 17, 2020 (See Github)
Additional features aside, the names are not compatible according to the explainer.
Comment by @zhangyongjing Jun 18, 2020 (See Github)
Additional features aside, the names are not compatible according to the explainer.
This is can be fixed easily and is under discussion, but it's also subject to the naming convension that the community needs to agree on (e.g. short_name vs shortName).
Comment by @xfq Jun 18, 2020 (See Github)
@cynthia See https://github.com/w3c/miniapp/issues/94
Discussed
Jun 22, 2020 (See Github)
[discussing TAG feedback on miniapps]
Sangwhan: does webapp manifest allow for extensibility?
Kenneth: yes you can do this...
Dan: do we need to create a new doc for "web app lifecycle" which incorporates both PWA and MiniApps? There's an old PWA lifecycle doc...
Sangwhan: we could suggest adding some new editors...
Dan: feels like a lifecycle doc should document things from a developer perspective.
[bumped and Sangwhan will work on fleshing out the doc for next week
Comment by @siusin Sep 3, 2020 (See Github)
Follow-up discussions:
- the TAG suggested to extend the WebApp Manifest for MiniApps
- MiniApp Virtual Meeting 2020-07-30, 2020-07-31
- WebApps Manifest & MiniApp Manifest Editors' Meeting 2020-08-26
Comment by @cynthia Sep 24, 2020 (See Github)
We were told that this is being re-worked as an extension of Webapp Manifest - we'd like to revisit this review when that work is done. Please let us know when you have an update!
Comment by @zhangyongjing Sep 25, 2020 (See Github)
Sure. We'll post the update here once available.
Comment by @xfq Nov 16, 2020 (See Github)
The pull request to re-work MAM as an extension of the WAM has been merged. See https://github.com/w3c/miniapp/pull/136
Discussed
Jan 1, 2021 (See Github)
Proposed closed
Comment by @cynthia Jan 26, 2021 (See Github)
That's great news! Aside from that detail we are happy to see this work move forward.
Comment by @kenchris Jan 26, 2021 (See Github)
It seems that it would be great if the keys would follow the TAG guideline for naming, ie use underscope:
Comment by @xfq Jan 27, 2021 (See Github)
It seems that it would be great if the keys would follow the TAG guideline for naming, ie use underscope:
I filed https://github.com/w3c/miniapp/issues/155 to track this.
Discussed
Jun 28, 2021 (See Github)
as above
Comment by @torgo Jun 29, 2021 (See Github)
We're going to close this for now and we look forward to reviewing when you have a manifest extension proposal for us to look at.
OpenedJun 12, 2020
Hello TAG!
I'm requesting a TAG review of MiniApp Manifest.
MiniApp Manifest defines a JSON-based profile file that provides developers with a centralized place to put essential information associated with a MiniApp. Such information include the basic metadata of a MiniApp as well as configurations regarding version control, window style, page resources, permission control etc.
Further details:
You should also know that...
The attribute list in the MiniApp Manifest would be further extended so as to provide more feature settings of the MiniApp as the project progresses. Other useful attributes from the Web App Manifest may also be mirrored (see Explainer) when the MiniApp community agrees on the necessity.
We'd prefer the TAG provide feedback as (please delete all but the desired option):
🐛 open issues in our GitHub repo for each point of feedback