Native or the Web? It's not a problem.

Objective

Mobile app is the URL and search engine revolution, today mobile app development seems to appear two major camps, Native and the Web, each think they represent the future trend, Native operation Smooth, rapid, relatively short Web development cycle, but also easy to cross the platform, but, What is the actual application of the project? Next, we do a comparative analysis based on the developer's discussion, and we know the answer.

Comparative analysis

	Native App	Web App
advantage	1, user experience stable, fluent 4, user viscosity high 6, direct manipulation of local resources 1, fix bugs only need to iterate update server side, no need to upgrade client 2, H5, JS cross-platform stress-free, low deployment cost
Disadvantage	1, the development cost is high: the function consummation only then may go on the line, also waits for the approval, Fix The bug should be fully upgraded; 2. High cost of transplantation: Android, Windows, IOS each platform to maintain; 3. The operation and promotion of each platform are different;	1, the entrance is not obvious (browser navigation, hyperlinks) 2, the user is not easy to remember, low retention rate, promotion reduced to one-time 3, the implementation are on the server side, not offline use, the network and Internet is extremely dependent on 4, the actual project, the user experience is not smooth 5. Developers cannot directly manipulate local resources 6, 8% of users are still using Android 2.3,webapp can not run smoothly 7, can not call the gyroscope and other sensors

When you finish this form, you suddenly find that the advantage of native is the disadvantage of the web and vice versa . :

JS Performance Comparison of x86 and ARM architectures

　　

This is a comparison test done by a foreigner, please look at the comparison data, the first is the Sunspider performance test:

Later the authors added their own iphone 4S for comparison;
Can see the x86 architecture of the PC relative to the arm architecture of mobile devices, x86 more suitable for running JS;

The ARM architecture program must be 10 times times more performance to be compared to the x86 architecture program, but not to the x64 architecture;
From a hardware perspective, it is unrealistic to expect the performance loss of this part to be stretched by Moore's law, because higher CPU frequency will lead to higher heat, the mobile device can not install a cooling fan or liquid nitrogen cooling, so from the use of equipment properties, ARM performance has been limited;

Unless, at the atomic level, quantum computers are already on the phone, the first commercial quantum computer D-wave has yet to be recognized:

Does this huge volume make you think of the first computer, full of Eniac in the room? History is always strikingly similar ~

　　This is D-wave's ad, yes,you can has one ...

Well, hand a quantum computer, wait 35 years, 2050 should be able to achieve, when the AI fully evolved, all kinds of robots all over the streets of the shops, through the delivery of fast food, express horse highway;

Go ahead and watch Native and the Web app~.

Web app developers say

"So even so many experts in the above BlaBla constantly said H5 how cow, but we still do not feel H5 good, still very confused, even I feel that the above speech are some confused, this confusion spent 2013, passed 2014, ushered in 2015. ”

"From the current situation, it is certainly the native app is the mainstream, have to admit that most of the current web app is too difficult to use, or even useless." A few days ago, I saw someone on the reader sharing an app that could turn the Web into an Android app, which is an indirect way of saying that web apps are really hard to use. "

native developers say

From the engineer's point of view, of course, I hope that the Web app is the mainstream, the vast number of engineers from one after another native app freed up to do more meaningful things. ”

However, any product development will put the user's experience in the first place, the user first, employees second, the third shareholder;

Conclusion

Native and Web The two are complementary, who can not replace who, a yin and Yang said, Tao consistent, the best solution is: Fusion ~

So how exactly does the development blend in? You can refer to this form:

Native	Web	Tips
Large number of interactions	Browse Content	A lot of interaction is multi-user, real-time input, selection, and so on, with native
Stable on-line	Trial and Error prototypes	H5, JS Development prototype rapid trial and error cost is low, once the prototype is determined to use native development on-line
accessing hardware	Content display	The web does not support the operation of various sensors, if the gyroscope, accelerometer hardware operation, only native
Development Core	Ancillary services	To learn, core functions with native development, auxiliary, partial browsing, low utilization of services with the web

At this point, Native or the Web, we finally have the answer, no longer impatient the tangled in how to choose, a deep, long Shi repair ~ Peace of mind to do Native;

You will know how to deal with the problem if you discuss it again in the next meeting.

Native or the Web? It's not a problem.