If HTML5 applications can emerge in the short term, Microsoft's WP7 will not benefit a lot or even succeed. If HTML5 applications can emerge in the short term, Microsoft's WP7 will not benefit a lot or even succeed. Reply: Technically, it is unlikely that HTML5 applications and games will be smooth and integrated into native applications within one year. HTML5 can only be used for simple applications (such as browsing). native apps have great advantages.
I personally think that HTML5 is not a bad thing for everyone. Although it is not mutually beneficial, it is a win-win situation. HTML5 applications are far from powerful in making killer applications, so they do not pose a great threat to any platform. Users cannot switch from ios to android because of an HTML5 application, and vice versa.
I don't know whether the HTML5 support of WP7 is good, because currently HTML5 is mainly based on webkit, and the support of other platforms is very labor intensive.
In short, the biggest beneficiaries of HTML5 are developers and users. devices supporting HTML5 provide users with more and better experiences. HTML5 is a cross-platform. It is supported by all three platforms and cannot be promoted to a certain platform. Currently, IOS also has many HTML5 WEB apps.
It will take another year for HTML5 games to reach the general effects of native applications. It is estimated that many games are ready to play.
I think the more impact is the emergence of HTML5-based mobile phone page games. users do not need to go to IOS or Android to download them. Open a page and install shortcuts to the desktop, or when you go to FACEBOOK's mobile phone version, you can directly play mobile social games by opening the components. This may be an application that has an impact on the app store. There are two types of HTML5-based applications.
- Browser based
- Webview based
First, although the functions are relatively rich, different browsers have different implementations, and the network is a fatal injury. for example, if everything is downloaded at one download, isn't the loading time too long? If ajax and other technologies are used to load data in batches, can they run properly in poor signals?
The second is simple and lightweight, and can solve the first problem. however, the performance is not high, the available javascript is limited, and the native api is required as a bridge for interaction. It is even worse that ios apps are sold to the Apple store.
How do mobile users know you as an html5 app?
How do I remember and open your website?
Do browser paid navigation?
Of course, ios cannot be used with android. There are too many android users, and Apple is fighting the world by one.
However, the high-end customers who are willing to pay for it are all in apple...
The world has a lot of cars, but BMW and Mercedes-Benz are still very moist and may not be the most users. However, android's dead point is too open to unify hardware specifications, which is very troublesome for developers. Application quality is far more important than quantity. You cannot develop an android Application with excellent compatibility. It is also a webkit kernel browser, which is obviously better supported by safari For html5 and css3. The html5 standard skin may not be finished yet ...... Alas, html5 is a good app, and games are not efficient. I don't know why you think that iOS and Android will have no chance after the rise of HTML5. I don't think this is a technical problem. On mobile devices, Native apps and Web apps are only technically different, and there is no difference in business models.
Apps Are mainstream on touch screen smartphones. What if you write it in HTML 5? Do you expect users to enter a URL in a browser to access your game/application? Impossible. You only need to make an App and put it on the user's home screen. the user clicks the icon on the home screen to access your game/App. In this case, what is the difference with Native apps? Besides, how do you ensure that the user is used offline? You still need to save it on the terminal. This is still a Native App, but it is not written in Objective-C. In the future, Apple will provide a framework that allows you to directly write applications using HTML. Your application will be published through App Store, and you will still be charged if you want to make a profit, you still need to rely on the App Store. You still need to allocate 30% yuan to Apple for how much you sell.
Even if someone has implemented a Web App navigation and put it in a browser, they want to create an App Store for the Web App. However, Apple and google can do the same, and they control a large number of users, mature payment channels, operating systems and browsers. These underlying platforms also cultivate user habits. In the end, these channels are still under control. You don't have to worry about big data. Because you will always be their downstream.
If we really want to compare the changes in the mobile device market after HTML 5 is widely used, I think HTML 5 is a cross-platform tool, but the API provided by this tool is not enough. In the future, Apple and Google will still be able to use private APIs to make HTML 5 not fully cross-platform (for example, access to GPS). The standards of HTML 5 are actually controlled by them. There are opportunities for WP7, but the iOS and Android that WP7 can do can also be quickly followed up. Marketing and user experience are the final challenges for the big guys. WP7 can surpass iOS and Android. 1. HTML5 Web App growth will inevitably affect Native apps, but I think it is benign for the entire mobile Internet, and web terminals have too many advantages for mobile devices, from the aspect of promotion and platform compatibility, it is even more important that the current APP market is too saturated, and solomo is used to develop apps.
2. I don't think the gap between IOS and Android will be affected.
