Weex is a client-side technology on the surface, but in fact it connects the whole way from the local development environment to the cloud deployment and distribution.
In the cloud, developers can deploy the generated JS bundle. And then it can be requested or pre-fetched from a mobile app with WeexSDK.
Even if a user does not install the App, he can still open a same web page in the browser, using the same source code.
In addition, the management of a Weex project is also very familiar with a web project. First, web developers can use npm packages to manage dependencies. Second, web developers can refer to all best practices from every process of a web project such as scaffolding, development, preview, debugging, test etc.
Also same as the best practice of web development, each Weex page will be built into a JS bundle. In the browser, we put JS bundle into the web page as a
<script> tag. In the client, we put JS bundle into the local, and execute it in WeexSDK.
- Platform differences between Weex and web
- Differences of using Vue between Weex with web
- Get Started
- Using Devtools
Weex JS bundle can be deployed and distributed as a static resource. Almost all current web development system and best practice can be applied to Weex directly such as generating JS bundle through CMS system or deploying JS bundle to static CDN, monitoring JS bundle traffic through server log, caching or pre-fetching JS bundle to reduce networking cost etc.
Although Weex has provided a group of most commonly used components and modules officially. But we definitely know they couldn’t satisfy everyone. So we design our native render as extendable as possible. You can extend more components and modules on your own. We can build and share an Weex eco-system together.
- Differences between Weex and web standard
- Using Weex in iOS
- Using Weex in Android
- Extend to iOS
- Extend to Android
Besides iOS and Android client, Weex also has a web version based on Vue 2.0. Developers can just use Vue 2.0 to build the same page in browsers.