-
Notifications
You must be signed in to change notification settings - Fork 48
The 1st CJK Meeting on MiniApps, 2021 04 08
Fuqiao Xue edited this page Apr 7, 2021
·
8 revisions
Meeting participants can edit this wiki page to add their own questions.
MiniApp vendors build complete ecosystems for users based on the hosting application or operating system.
Questions:
- What technologies/services does the MiniApp ecosystem include, and in which scenarios can they be applied? What are the differences between different MiniApp forms?
This topic is about the technical architecture of MiniApps, such as the hosting runtime, manifest files, package structure, etc.
Questions:
- Why did MiniApp platforms choose a technical architecture different from that of traditional Web applications? Are there differences in the technical architecture between different MiniApp platforms?
Because there are many different MiniApp platforms, in order to make cross-platform development more convenient, developers can utilize cross-platform frameworks.
Questions:
- According to my understanding, MiniApps are not completely consistent with the existing frontend webdev ecosystem, and have a special multi-process/thread architecture and DSLs. Do MiniApp frameworks use a methodology that's similar to the current MiniApp DSLs and APIs, or do the frameworks use a model that is closer to traditional Web development?
- How do MiniApp cross-platform frameworks deal with inconsistencies between different platform components and APIs?
- If the MiniApps standardization is successful, will the frameworks provide a migration path?
MiniApps have also been used in some new scenarios, such as IoT and automotive.
Questions:
- In addition to the traditional mobile phone scenarios, what are the new scenarios? Is there a plan for incubation/standardization it in the MiniApps CG and/or collaborating with existing W3C groups?
- What is the difference between MiniApps in different scenarios?
- How to ensure the implementation of standards?