The difference between uniapp and HTML5

The difference between uniapp and HTML5: 1. uniapp is a framework that uses Vue.js to develop all front-end applications, while HTML5 is a language description method for building web content; 2. uniapp does not support dom operations, while H5 There is a DOM object on the end; 3. Uniapp does not support filters, etc.

The operating environment of this tutorial: windows7 system, uni-app2.5.1 version, thinkpad t480 computer.

Recommendation (free): uni-app development tutorial

uniapp is a framework that uses Vue.js to develop all front-end applications. Developers write a set of codes to Publish to iOS, Android, Web (responsive), various mini programs (WeChat/Alipay/Baidu/Toutiao/QQ/DingTalk/Taobao), quick applications and other platforms.

HTML5 is a language description method for constructing web content. HTML5 is the next generation standard of the Internet and a language method for constructing and presenting Internet content. It is considered to be one of the core technologies of the Internet. HTML was created in 1990, and HTML4 became an Internet standard in 1997 and is widely used in the development of Internet applications.

Uniapp supports cross-mobile development. If you only do H5 end, using uniapp is actually no different from using vue for development. The plug-ins that can be used by vue can also be used by uniapp.

The performance problems of uniapp are mainly concentrated on the app side. The development experience of H5 and VUE is the same.

1. Differences in tags

2. Differences in components

3. Changes in JS

4. Main differences

uniapp The main difference from h5 is that uniapp does not support DOM operations (the H5 side has DOM objects) and does not support filters, which is consistent with the WeChat applet.

5. Common points

1. The common advantages of uniapp and h5: one end is multi-purpose, good for a single variety, simple, convenient, and compact.

2. The common shortcomings of uniapp and h5: compared with native, there is currently an unbridgeable gap in performance.

6. APP application architecture

uni-app can be compiled and packaged into a WebApp. Why do many people still use native APP shells? Doesn't this increase the burden? In fact, this is determined by the needs of the project. First use uni-app to develop the H5 end. For the time being, uni-app cannot achieve the goal, and then use the native APP to complete the interaction to meet specific needs.

1. Development aspects

(1) Native APP

Different mobile operating systems (iphone, ipad, Android) need to be developed separately. Development and maintenance costs are high, development speed is slow, and the APP online review process is complex and slow.

(2) WebApp

Because it runs on the browser of a mobile device, only one development project is required. The development cost is low and the development speed is fast.

2. In terms of functions

(1) The native APP

can call the hardware devices of the mobile terminal (microphone, camera, SMS, GPS, Bluetooth) to achieve rich functions.

(2) WebApp

is more of a page display APP than a computer-side web page. Only limited mobile hardware device functionality is available.

3. Application installation and version control

(1) Native APP

Installation: App Store|APP Store download, which can save bandwidth costs and access local resources. cache.

Version: Users are free to choose whether to update the version. Both old and new versions need to be maintained, and the maintenance cost is high

(2) WebApp

Installation: Accessed through the browser on the mobile device, software updates only require updating the server

Version: No installation is required, saving the memory space of mobile terminals. All users have the same version. The version update speed is convenient. Just update the data directly on the server and go online immediately

4. In terms of loading speed

( 1) The native APP

is composed of "cloud server data application client". All UI elements, data content, and logical framework of the APP are installed on the mobile terminal. When accessing, only the data needs to be loaded, and the application page frame does not need to be downloaded, so the loading speed is faster and the page response is faster. Can be used offline.

(2)WebApp

To open a page, all elements of the page need to be reloaded. The access speed is limited by the performance of the mobile terminal and the network environment, resulting in slow loading speed and frequent and easy operations. Stuck.

5. Hybrid APP

Advantages: compatible with multiple platforms, smooth access to mobile device functions, app store download (web application uses the shell of native application)

Disadvantages: user experience Not as good as native, performance is slightly slower

6. Summary

Native APP prefers interaction and focuses on user experience; Web App prefers simple interaction with the browser for information display. Some functions require access to hardware, so use the native APP.

The popular method now is to integrate the native APP with the Web App. The core functions use the native APP, and the auxiliary simple functions such as content display use the Web App. This facilitates updates and ensures the interactive experience of core functions.

The above is the detailed content of The difference between uniapp and HTML5. For more information, please follow other related articles on the PHP Chinese website!