W3C

– DRAFT –
MiniApps WG Teleconference

25 August 2022

Attendees

Present
Dan_Zhou, martin, QingAn, Thomas_Steiner, xfq, Xiaoping_Zhao, xiaoqian, Zitao_Wang
Regrets
-
Chair
Dan_Zhou
Scribe
xfq, xiaoqian

Meeting minutes

TPAC

<xiaoqian> https://tpac2022-china-hub.netlify.app/#/miniapp

xfq: the detail agenda is not ready yet
… first part is the Hackathon for MiniApps specs
… second part is the MiniApps WG meeting, specs status and plan
… third part is the CG meeting, a few proposals
… 6 talks, one from Zitao_Wang about standard design
… one from the Taro team of JD.com
… one from QingAn about MiniApp on Vehicles
… one from Finogeeks about MiniApps in enterprise
… one from Dingdao, about Manifest
… one more from Microsoft, about PWAs and MiniApps

Zitao_Wang: @@

[explain the MiniApps Frameworks and specs]

Zitao_Wang: it would be great if we can show the architecture of a miniapp framework in the Hackathon
… JD Taro can be an example
… but we need to think about the next steps
… do you think this should be part of the Hackathon or the CG meeting?

Dan_Zhou: what's the plan for the WG meeting?

Zitao_Wang: I think the testing project is one of the important steps of our specs development
… we can Cfp in this meeting
… we are also looking for speakers from other vendors
… Qing An can introduce MiniApp on Vehicles
… we can also introduce our conversion tools in the Hackathon
… the joint project of the Huawei, Baidu and Alibaba
… to show support from these 3 vendors

https://github.com/w3c/miniapp/issues/194

xiaoqian: I have a question for martin and tomayac
… I wonder if you'd like to join the WG meeting
… and if so, do you need multi-language support?

martin: if I can, I'd be glad to join

xiaoqian: the Hackathon is in the morning, which isn't an ideal time for you
… but you can join the WG and CG meetings

<tomayac> Time permitting (and given translation), I'd be happy to attend, too. Likewise, I'd be interested in reading the summary.

Lifecycle

QingAn: Lifecycle has completed privacy, a11y, and i18n review
… I'm working on addressing the comments

https://github.com/w3c/miniapp-lifecycle/issues/32

QingAn: I've looked at other lifecycle specs
… but didn't see accessibility-related text
… will work with PING
… to address this issue

https://github.com/w3c/miniapp-lifecycle/issues/31

QingAn: simple one
… will try to provide more detailed explanations

https://github.com/w3c/miniapp-lifecycle/issues/30

QingAn: I've sent a PR
… I have discussed this issue with Xiaomi
… and PING made a similar comment
… I'm trying to use events instead of callbacks
… still need time to evaluate if the PR satisfies the requirements
… Page Lifecycle also uses addEventListener instead of callbacks

Dan_Zhou: thanks
… any comments?

QingAn: if would be good if you and Zitao can review it

Zitao_Wang: will do

Dan_Zhou: ok

Manifest

<martin> https://github.com/w3c/miniapp-manifest/issues/43

martin: this issue is about the alignment of MiniApp's app_id and Web App Manifest's id member
… raised by tomayac
… I already raised an issue against Web App Manifest
… MiniApps don't have document URLs because it's distributed in multiple ways
… it's still open
… IMO if we can adopt the id from Web App Manifest it would be great
… but no news so far

<martin> https://github.com/w3c/miniapp-manifest/issues/54

martin: this is something I can do

<martin> https://github.com/w3c/miniapp-manifest/issues/55

martin: based on the text in the white paper

martin: PING is asking how to validate / verify app_id
… I will work on this issue

<martin> https://github.com/w3c/miniapp-manifest/issues/56

martin: this is also from PING
… asking for clarification on "sessions"
… if you have any comments feel free to comment on the issue

<martin> https://github.com/w3c/miniapp-manifest/issues/57

martin: this issue is raised by tomayac

<tomayac> (Noting that there's no accepted solution yet, so having mini app requirements be part of the discussion would be very much welcome!)

martin: similar to #43

<Github> https://github.com/w3c/miniapp-packaging/issues/3 : Discussion of page configuration file

martin: if we can do it, we're happy to align with WAM

martin: no new PRs or commits this month

Dan_Zhou: maybe we can clarify the relationship in the explainer

martin: yes, and add notes to the spec

Packaging

martin: wide review has started
… I know we will get some comments
… because we're missing an important part of the packaging
… the "content" of the miniapp
… HTML/CSS/JS
… so far I've included some "placeholders"

https://github.com/w3c/miniapp-packaging/issues/30

Testing

https://github.com/w3c/miniapp-tests

[martin introduces the structure of a test]

https://github.com/w3c/miniapp-tests/issues/7

martin: xfq raised an issue about how to run the tests
… I wrote some information on how to write tests and generate reports
… I created some tests about manifest, packaging, and lifecycle
… feel free to try it
… so far we cannot test the MiniApps, but hopefully we can test them in the near future
… using the conversion tool or whatever
… the .ma files are the packages themselves
… please have a look

Addressing

Dan_Zhou: no progress

Widget

Xiaoping_Zhao: updated the PR a bit, nothing worth mentioning
… can talk about it in next month's TPAC

Dan_Zhou: next meeting is TPAC

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).