The way of APP technology evolution


Talking about app, everyone is too familiar with it. Today I want to talk about the way of technology evolution for so many years.
In the early days, some large companies began to make some apps, such as Facebook, Google and other foreign companies have developed this technical route. At that time, the number of apps was very small. Basically, we can understand that the app in the Web era was implemented in the way of web. At that time, we heard the voice of HTML5. At that time, everyone said that H5 would be in the Jianghu together in the future. At that time, Android was also very divided, and the same code had to be divided into many parts. So there was a voice like that.
With the progress of the times, when the iPhone 4 was released around 2010, we can see that a large number of applications came along. All kinds of technologies have appeared correspondingly, but mostly in the direction of H5. At that time, there was the emergence of phonegap (earlier), which can realize rapid app development. In 2012, from Facebook, we learned that “Zuckerberg himself admitted that too much betting on HTML5 is the biggest mistake.” We can also see some clues from the development of Facebook’s app. First of all, this kind of cross era thing, such as when HTML5 came out, also had this problem. You’re going to write JS bridging, which leads to a growing volume. Next, we will find that the bridging code is very messy, and the UI on each platform needs to be compromised, which is not good-looking or particularly easy to use on each platform. Finally, one of the most annoying problems for front-end engineers is that browsers are not standardized and compatible. Therefore, mobile development should also consider compatibility related issues. In addition, we have made so many investments that the complexity of all technologies is objective. What you need to do is to use the company’s approach to solve the objective complexity. If you want to be lazy, in the end you will find you can’t afford to go. The key point is that at that time, app was not customized for users, but for our engineers. These are all problems. Therefore, your product strategy should be based on the user experience, rather than on how a certain technology is driven.
In the future, we can see that more enterprises return to the path of pure native development, and we all realize that pure native app development is the right way. So we develop in this direction. Now, react native of Facebook, weex of Ali, deviceone of cup, react native and weex all use js to write the syntax of Android and IOS. You need to see it The SDK of Android and IOS. Deviceone uses JS to visualize the UI. All components are purely native. You can program without looking at the SDKs of Android and IOS. Basically, these three platforms are modular. If you have the energy to learn the SDKs of Android and IOS, you can use the first two platforms. If you want to develop apps quickly and don’t want to know the SDKs of Android and IOS, you can try deviceone.
I believe that in the next few years, there will be innovation in app technology, and we are looking forward to the next era.

Recommended Today

ES6 array sorting: more recommended methods and techniques than Es5

Original link: HTTPS: / / dsx2016. COM /? P = 692 WeChat official account: Senior brother 2016 ECMAScript ECMA ScriptyesECMA-262The name of the standardized scripting language. althoughJavaScriptandJScriptAndECMAScriptCompatible, but contains more thanECMA ScriptFunction. The following table is divided into four modules: ECMAScript 1st Edition (ECMA-262)Corresponding to the first edition andES5Previous versions (this article only) ECMAScript 5.1 […]