In recent years, operating systems and hardware vendors have tried to build their own application platforms and moat, represented by Facebook's Sparta project and Amazon's browser-based KindleCloudReader, all attempt to build a platform on a standard webpage to break the application platform sharing rules. Will the Web Platform eventually surpass the application platform on the mobile platform? Why? In recent years, operating systems and hardware vendors have tried to build their own application platforms and moat, represented by Facebook's Sparta project and Amazon's browser-based Kindle Cloud Reader, all attempt to build a platform on a standard webpage to break the application platform sharing rules. Will the Web Platform eventually surpass the application platform on the mobile platform? Why? Reply: I have asked a former Apple employee this question. He believes that it will not take a long time, because HTML5 is a set of standards, and it will certainly take into account a wider scope of application, therefore, standards are always falling behind in the industry, while mobile is currently developing rapidly, and standards will constrain innovation. His suggestion is that if your application requires an advanced experience, you must use the Native client.
To answer the same question, Dr. Zhao, the technology expert, said: mobile Web has great advantages, especially development costs, which will attract more and more investment. It does not need to be discussed too much in the future. It will certainly look like the current PC-side situation. Cloud computing is a general trend, but it cannot negate the value of the end. Today, terminals provide increasingly powerful computing capabilities, integrate more and more sensors, and provide more and more natural operation experiences, a universal HTML5 standard, it is impossible to take special care of the unique advantages of each specific terminal, which can only be satisfied by the terminal's own App Store. Therefore, the Web platform cannot replace its own App Store.
On the other hand, it is possible for the Web platform to break through the application platform. This is mainly from the perspective of development and release costs. Most enterprises cannot take into account multiple application platforms at the same time, and most applications do not need the support of specific hardware or specific sensors. For these enterprises, HTML5 is universal enough, you do not need to consider the issue of product distribution and deployment.
In short, both the Web Platform and application platform have their own development space. Web platform gradually replaced Windows desktop applications
Last 20 years.
- The emergence and prevalence of web technology, network interaction applications reach or close to the level of desktop programs
- The popularity of broadband makes the network loading and response speed reach or close to the desktop program level
Due to the limited size of mobile phones, the Web Platform on mobile phones is more insufficient than the application platform.
- The maturity of Html5 technology makes the network program user experience reach or close to the App level
- 3G/4G popularity to Ensure network speed
Facebook's Sparta project and Amazon's browser-based Kindle Cloud Reader are currently all defensive strategies. Mobile Web platforms lag far behind apps in terms of user experience, speed, and performance, in the next five years, we should not see any hope of transcendence.Aside from specific market strategies, I personally think it is more a philosophical choice.
For example, there was a debate between WORA and native before HTML5 emerged. But it does not mean that native must be more elegant than WORA. The key is to see how your application functions and positioning it.
Of course, as a practitioner, we may look at this issue from the development stage of the team. HTML5 can be deployed and modified more quickly. So in the idea verification phase, this method is used to discard some native splendor. Why? When your idea is accepted by users, it is not too late to increase investment and make an elegant native client.
Always remember that what wins is the team's idea and executive power, rather than the choice of a certain technology. Within three years, it cannot be met.
In the past, I had the illusion of replacing Native with html5. after nearly a year of practice, the fact tells me that html5 web apps still have a long way to go.
Html5 supporters believe that the advantages of Html5 are concentrated on low development costs, cross-platform, and no installation. The problem is that these advantages are not worth mentioning in the face of the performance and stability of Html5 compared with Native.
In the end, your App targets users. users do not care about your development costs, or even cross-platform applications. Users are most concerned about whether the App can provide the best experience. In this regard, native wins.
However, I am still optimistic about the future of Html5. As a developer, it is a more reliable choice to combine Html5 and Native technologies. the future is not easy to say. Basically, the Chinese are following the old beauty. For the moment, from the perspective of improving the development speed, compatibility, and version update of the app, the more reliable compromise is based on the local application as the framework of different platforms, some use html5 to implement features that often need to be updated. It is more suitable for applications that focus on practicality. For games and other applications that require fast response and High smoothness of operations, it takes n years for html5 to catch up with local applications or flash. I used html5 for two web apps in ios. My experience is: For a long time, html5-based web apps cannot replace native apps.
First, html5 is a standard, but browsers on different platforms have different levels of support. As a result, web apps can only use the functions supported by various browsers.
Secondly, compared with native apps, html5 has insufficient capabilities.
Third, the efficiency and performance of web apps are much lower than that of native apps.
Therefore, to provide excellent user experience, native apps must be developed.
