Cross-platform, consider H5, many tools are already very complete such as apicloud. The difference between native and H5 is the cross-platform issue. Waiting for win10.
It is recommended to start learning from the native version first. Hybrid applications are also modules developed from native languages and written as interfaces for js to call
I don’t think there is a decisive gap between the two to have a perfect answer.
I suggest you consider the following:
1. Do you have a foundation in Java or web development? If you already have a foundation in Java, it is recommended to give priority to native APP development
2. Do you have performance requirements? If the project is sensitive to performance, then native APP is the only choice.
3. Do you have your own ideas for future development?
The development directions of the two after APP development are different. I’m not sure about H5. In the future, native application development can include Android phone security, Android system kernel, Android transplantation (for example, the shopping guide machines in large shopping malls have changed from the previous XP to Android systems), etc.
In terms of future (money), I think both are situations where low-quality personnel are rampant and excellent talents are lacking. I have personally come across many startup companies that are willing to recruit developers at a much higher price than BAT, so this aspect is Don’t worry~
It’s better to learn native first, after all, h5 is still imitating a lot of native interactions and animations. Understanding the principle of native is still more helpful for h5.
The biggest advantage between h5 and native is that it is cross-platform. The development cost of native App is much more than that of h5, but native App has some things that h5 cannot achieve, such as smooth operation. Now there is a way to embed h5 into native app, but wouldn’t this castrate the biggest advantage of h5 over the native app? . . . . Recently, I have been thinking about this issue as well. . . . . . . I am halfway through android development
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Native.
If you use it well, you can consider a hybrid framework
If you only do Android development, please decisively learn native
Why not learn them all?
Of course, learning is from the native place.
Cross-platform, consider H5, many tools are already very complete such as apicloud. The difference between native and H5 is the cross-platform issue. Waiting for win10.
Mr. Why not consider iOS.
It is recommended to start learning from the native version first. Hybrid applications are also modules developed from native languages and written as interfaces for js to call
I don’t think there is a decisive gap between the two to have a perfect answer.
I suggest you consider the following:
1. Do you have a foundation in Java or web development? If you already have a foundation in Java, it is recommended to give priority to native APP development
2. Do you have performance requirements? If the project is sensitive to performance, then native APP is the only choice.
3. Do you have your own ideas for future development?
The development directions of the two after APP development are different. I’m not sure about H5. In the future, native application development can include Android phone security, Android system kernel, Android transplantation (for example, the shopping guide machines in large shopping malls have changed from the previous XP to Android systems), etc.
In terms of future (money), I think both are situations where low-quality personnel are rampant and excellent talents are lacking. I have personally come across many startup companies that are willing to recruit developers at a much higher price than BAT, so this aspect is Don’t worry~
It’s better to learn native first, after all, h5 is still imitating a lot of native interactions and animations. Understanding the principle of native is still more helpful for h5.
The biggest advantage between h5 and native is that it is cross-platform. The development cost of native App is much more than that of h5, but native App has some things that h5 cannot achieve, such as smooth operation. Now there is a way to embed h5 into native app, but wouldn’t this castrate the biggest advantage of h5 over the native app? . . . . Recently, I have been thinking about this issue as well. . . . . . . I am halfway through android development