Baidu novels launched HTML 5 Web applications designed for tablets. The experience is similar to that of native applications. Does it mean that with the maturity of HTML5 technology, native applications will be lost to webapps in the future? -

See weibo. com1874255663xh1jrom4w. Visit m. baidu. comxs on a tablet such as an ipad, and you will also see that the interface is dazzling and will not be lost to nativeapp. In the desktop application field, native applications have lost to webapps. If html5 is more mature in the future, will nativeapp also lose to webapps in the mobile application field? See http://weibo.com/1873795663/xh1JRom4w for what I saw on Weibo
Access http://m.baidu.com/xs with tablets like ipad You can also see that the interface is very dazzling and won't be lost to the native app. In the desktop application field, native applications have lost to web apps. If html5 is more mature in the future, will native apps also lose to web apps in the mobile application field? Reply content: This is too early, for several reasons

1) html5 standards are being improved. Although promising, apps are constantly evolving. Further, apps and hardware are more integrated to better utilize the high performance of hardware. For the moment, the trend is still a trend, and the reality cannot be imagined.

2) Let's give an example, not to mention that the sample is too small and the sample is not typical. It is difficult to deduce the conclusion you want. The small Baidu html5 sample you see does not represent much.

3) In the desktop application field, native applications have already lost to web apps-even more difficult !! This assertion is inappropriate. At present, web apps can only handle some relatively simple work. The efficiency of large software such as PS is not achieved overnight by web apps. In the future, the boundaries between native apps and web apps will become increasingly vague and will be complementary. Whether an app is native or html5 will not cause too much discussion. Now, even if you do native apps, many will inevitably use html technology.

Compared with native apps, web apps have some disadvantages in system-level operations. However, there is also a trend to integrate web app technology with native technology. The rise of frameworks such as PhoneGap directly uses javascript as an intermediate layer, this allows web apps to implement system-level functions that cannot be implemented by html5.

For an app developed by such a framework, do you say it is a web app or a native app? In the future, the boundaries between native apps and web apps will become increasingly blurred ...... Html5 itself is developed to solve the html client-based process. If this path goes on, html will gradually blur the difference with the app.

Now we are concerned about the app or html, and users will not care about it in the future. In addition, many current apps are disguised as webapps. When I think about webapp, I always think about it as a front-end, so I always think about IE and UCWEB.

Currently, there are roughly two Webapp application scenarios:
1. The webapp running on the Chrome Desktop client of V8 is optimized based on Chrome's features. The example is offline GMAIL, Which is smooth;
2. Safari Mobile Webapp, which runs on the iPhone, features that the website adds the page to the background of the home screen by optimizing the features of Safari on the iPhone, open the website icon on the home screen and open an app. The app runs in Safari but does not have the Safari GUI. the required data will be downloaded when it is opened for the first time.
The example is http://mac.pcbeta.com

The conclusion is:
1. You need to make a webapp, but you still need to consider the Platform issues;
2. HTML5's availability in terms of interfaces, storage, and Socket is still inferior to Native.
3. Native apps and webapps are differentiated in terms of security and will exist for a long time.
4. js execution efficiency and resource occupation. Http://m.baidu.com/xs The first response is still regarded as an example, but I just clicked a notebook to go in, the return is only in the http://baidu.com The result returned when the domain name is searched, and it seems that most of the regions cannot be searched.

Yan, http://m.baidu.com/xs Not a web app-it is not an app at all.

If you want to analyze the web app, the best thing you do now is Kindle Cloud Reader (http://read.amazon.com ). ). But even now (August 2011), it cannot be compared with the native Kindle for iOS. No more objective answers than this PPT
Http://www.slideshare.net/retomeier/html5-or-android-for-mobile-development I used the ipad to see why I think the experience is far inferior to that of the native app. However, I agree that web apps are a trend. In the long run, html and app complement each other, while html can be considered for cross-platform scenarios. In addition, 'html5' is abused. In fact, it is a collection of various web technologies such as html, js, and css. If this concept is not thoroughly studied, html5 is enthusiastically promoted and ignored! Native apps and web apps have their own advantages. Although HTML5 has always been a future direction, it is a trend to replace native apps. However, it is not very obvious at present. At least native apps can implement many system-level functions. The simplest example is push. Pure HTML5 still relies on browsers, browser is actually a native app, and web apps are at a disadvantage in terms of underlying function implementation.
However, the flexible maintainability of web apps is also impossible for native apps. The combination of the two should be a good direction, if one day the browser can be upgraded to the system level or the web app has certain system-level functions, it will be able to compete fairly with the native app. Html5 is also html. I don't think you need to worry too much about who will overwhelm them. See what kind of native app is more suitable for your application. native NLP is better at upgrading convenience and cross-platform. Choose based on your application's specific needs.