This topic describes the terms that you may encounter when you use Enterprise Mobile Application Studio (EMAS) to develop native apps, HTML5 apps, and MiniApps. This topic helps you better understand EMAS.
Term | Description |
app | A specific type of terminal program that is released and deployed independently. App types include but are not limited to Android, iOS, HTML5, and desktop apps. |
solution | A collection of scenario-specific methodologies, design concepts, and service capabilities. Examples: cross-platform solutions and continuous delivery solutions. |
uni-app | uni-app is a framework that allows you to develop front end applications by using Vue.js. The same set of code can be published as a miniapp on superapps (like Alipay, DingTalk, Taobao, and WeChat), as native iOS and Android apps, or as a web application. uni-app has a community with millions of developers and applications. uni-app has been open-sourced on Github for everyone to use. For more information about uni-app, visit uni-app official website. |
WindVane | WinVane is an extensible solution for hybrid apps. It provides powerful, easy-to-use WebView containers for web applications in hybrid apps. WindVane adds a variety of features, such as URL filtering and events, for WebView objects. WindVane web applications can interact with the hosting hybrid app to utilize hardware functions. WindVane containers support miniapps and H5 applications. |
ZCache | ZCache is a performance optimization solution that is developed by Alibaba Cloud for HTML5 apps and mini programs. ZCache accelerates page loading and improves user experience in page visits. ZCache uses a resource package that stores locally preloaded pages to reduce the number of requests for resources on servers. This way, page loading becomes faster. For example, you enable the preload feature for a page. In this case, when a client accesses the resources of the page, the client first searches locally preloaded resources that are requested. If the resources of the page are preloaded, the client reads the preloaded resources. If the resources of the page are not preloaded, the client requests the resources of the page after the client accesses the corresponding server over network connections. We recommend you enable the preload feature for a page because resources that are included in an installation package increase the size of the package. You can check the preload outcome based on the hit ratio of ZCache. |