During the exploration phase, potential standard requirements have been identified due to the unique nature of MiniApp in comparison to the typical Web environment. Substantial research work and joint discussions with related W3C groups have been conducted to clarify the requirements and possible solutions for MiniApp standardization. For instance, the hosting platform may or may not be a browser, and the application construction may or may not be based on web resources. Therefore, different but relevant technologies are used for UI configuration and rendering, resource packaging, and the API access to local system capabilities. Such cases have not been fully covered by existing Web standards, such as Web Packaging, Web App Manifest, or Web APIs.
-The MiniApps Working Group expects to consider similar past activities and technologies, such as Packaged Web Apps (Widgets) and Firefox OS' Open Web Apps, as it works out how to build best for the Web's current needs and future. The MiniApps Working Group aims to harmonize the heterogeneous MiniApp ecosystem, enabling interoperability among the different MiniApp platforms, maximizing the convergence of MiniApps and the World Wide Web, reducing the development costs and facilitating the adoption of this technology.
+The MiniApps Working Group expects to consider similar past activities and technologies, such as Packaged Web Apps (Widgets) and Firefox OS' Open Web Apps, as it works out how to build best for the Web's current needs and future. The MiniApps Working Group aims to harmonize the heterogeneous MiniApp ecosystem, enabling interoperability among the different MiniApp platforms, maximizing the convergence of MiniApps and the World Wide Web, reducing the development costs and facilitating the adoption of this technology.