drafting a FAQ about the proposed MiniApp standards work

Dear MiniApp CG participants,

 

While we are moving the MiniApp standards work forward in W3C, especially
proposing the charter of MiniApp Working Group, some initial feedbacks have
been received. Some of the feedbacks express questions and concerns about
the possibility of MiniApp standards forking currently Web technologies. 

It would be very necessary for the MiniApp vendors to clarify the concerns
and justify the work of current MiniApp specifications. So I would like to
propose a FAQ document to explain the rationale behind the proposed MiniApps
standards work. 

Here are some initial question list in the FAQ. More questions and answers
are welcome on github issue #109[1]. 

We plan to make a draft of this document in the next week and encourage the
group input in your earliest convenience.  

1. Is MiniApp a part of Web Platform? What is the relationship between
MiniApp and Web Platform?
2. If MiniApp uses certain parts of Web technologies, how come it runs
without a browser engine?
3. How is MiniApp Manifest different from WebApp Manifest? Could
MiniApp Manifest become a unique case for WebApp Manifest? Could WebApp
Manifest be merged into the WebApp Manifest?
4. Why there is need to create a new URI Scheme specification? How to
use the new URI Scheme specification to handle origin? How to handle
SecureContext without origin? How to handle CORS?
5. Is it possible to harmonize WebApp Lifecycle, PWA Lifecycle and
MiniApp Lifecycle specifications? If so, how?
6. Is it possible for MiniApp packaging to leverage the existing
discussions such as signed exchanges and Web Packaging?
7. What is the implementation expectations of MiniApp specifications in
the globe? Are the implementations only expected from Chinese MiniApp
vendors?
8. Does MiniApp have its own security module?

[1] https://github.com/w3c/miniapp/issues/109 

 

Angel