The evolution of APP technology

When it comes to APP, everyone is too familiar with it. Today, I want to talk about the road of technological evolution over the years.
    In the early days, some large companies started to make some apps. For example, foreign companies such as facebook and google have already developed this technical route. At that time, the number of APPs was very small. Basically, we can understand that the APPs in the web era are all based on the web. way to implement the APP. It was at this time that we heard the voice of Html5. At that time, everyone rushed to say that H5 will be together in the future. At that time, the differentiation of android was also very serious, and the same code had to be divided into many parts. So there was that sound.
    With the progress of the times, around 2010, when the iphone4 was released, we can see that a large number of applications were born. Various technologies have appeared accordingly, but most of them are in the direction of H5. At that time, there was phonegap (earlier), which could realize rapid APP development. In 2012, I learned from Facebook that "Zuckerberg himself" I personally admit that placing too much bet 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-generational thing, such as HTML5, also appeared when it came out. question. You have to write JS bridges, which leads to an increasing volume. Next, you will find that the bridging code is very messy, the UI has to be compromised on each platform, and it does not look good on each platform, or is not particularly easy to use. Finally, one of the most annoying problems for front-end engineers is that browsers are not standardized and incompatible. Therefore, mobile development should also consider compatibility-related issues. In addition, we have made so much investment, the complexity of all technologies is objective. What you have to do is how to use the company's way to solve the objective complexity. If you want to be lazy, you will eventually find that you will not be able to eat and walk around. The most critical point, at that time, the APP was not tailored for users, but for our engineers. These are questions. Therefore, your product strategy should be based on the user experience as the starting point, not because of how powerful a certain technology is.
    In the future development, we can see that more companies have returned to the road of pure native development. Everyone realizes that pure native APP development is the right way, so everyone develops in this direction, and the current facebook appears. React Native, Ali's weex, Cup's deviceone, React Native and weex all use js to write the syntax of android and ios. You need to see the sdk of android and ios. Deviceone uses js to visualize the UI. All components are pure native. You can program without looking at the sdk of android and ios. Basically, these three platforms are modular. If you have the energy to learn the sdk of android and ios , you can use the first two platforms, if you want to develop APP quickly and don't want to know the sdk of android and ios, you can try deviceone.
    I believe that in the next few years, there will be innovations in APP technology, and we look forward to the next era.

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326633131&siteId=291194637