Comparison of H5, native app and hybrid development

First, the concept

A) H5: HTML5, who has been exposed to the Internet, is aware of HTML, so it is clear that H5 is a standard protocol for Hypertext Markup language that is the 5th major modification of HTML.

b) Native: Use native authoring app (Native app), which is based on the current smartphone's operating system (such as Android Android, Apple iOS, plus Windows Phone) and with native programming to write a running third-party mobile app, Referred to as the native app.

Second, the user angle of use

When an app is presented to the user, the most important thing the user cares about is that the user can do what I want with the simplest operation, or to complete some operations, regardless of how you implement the function, because to the user say most main is "user experience".

"User Experience" This is a top priority for program apes and business operators that must be considered.

The specific use of H5 experience good or with the original experience good, this involves the application itself and the various pages to determine the content.

H5 app Development Fast, realize the function is also very dazzling, good tall on Oh! That's the technology I want to achieve. Native development is too time consuming and laborious.
Native app can better adapt to various types of function implementation, you H5 can be my native can be realized.
h5+ native hybrid development, a fixed format and control of the page response speed requirements of the module on the use of native Natvie development, for news, large paragraphs of text, information class with H5 language standard implementation page to load, embed it into the native frame so, can achieve a better experience.

————————————————————————————————

Native app: Native app is unique to a mobile platform (such as iOS or Android), using the platform-supported development tools and languages (such as iOS platform support Xcode and Objective-c, Android platform support Eclipse and Java). The native application looks (looks) and runs up (performance) is the best.
HTML5 Applications: HTML5 applications use standard web technologies, typically HTML5, JavaScript, and CSS. The cross-platform mobile application, which is only written once and can be run around, can be run on multiple devices. While developers can build complex applications using only HTML5 and JavaScript, there are significant limitations to this article, including session management, secure offline storage, and access to native device capabilities (cameras, calendars, geolocation, and so on).
Hybrid applications: Hybrid applications allow developers to embed HTML5 applications into a thin, native container that integrates the advantages (and drawbacks) of native applications and HTML5 applications.

In short, native applications provide the best ease of use, the best features, and the best overall mobile experience. These are features that can only be implemented with native applications:
Multi-Touch: Double-click, Zoom, and other combined user interface (UI) gestures.

Quick Graphics API: Native platform gives you the fastest graphics to display. This feature may not be important if you display a static screen with only a few elements, but it's important if you're using a lot of data and need to refresh quickly.

? Smooth animation: Related to the Fast graphics API is the ability to achieve smooth animation. This is especially important in animations, highly interactive reports, or computational-intensive algorithms for converting photos and sounds.

? Built-in parts: cameras, Address books, geolocation, and other native features of the device can be seamlessly integrated into mobile applications. Another important built-in component is an encrypted storage device, which is described in more detail later.

Easy to use: the native platform is a familiar platform, so if you add all the native features that people expect on this familiar platform, you'll have a completely easier app to use.

? Documentation: There are more than 2,500 books on the market that only cover iOS and Android, and there are countless articles, blog posts, and technical posts on the StackOverflow website.

Native applications are typically developed using the integrated development environment (IDE). The IDE provides tools for building, debugging, project management, and versioning, as well as other tools that professional developers need. While iOS and Android apps are developed using different Ides and languages, there are a lot of similarities in the development environment, and there's no need to delve into the differences. In short, what tools are needed for your device, and what tools you use.

You need these tools because native applications are more difficult to develop. Similarly, the development experience required is richer than the other development scenarios, and you can't just clip the copy objective-c and hope it works. Indeed, the technical expertise of the development team is an important consideration. If you're a professional developer, I'm probably already familiar with proven APIs and frameworks, easy-to-implement effects with built-in widgets, or the benefits of putting code in one place. To be honest, this year's skilled native iOS or Android developers, like rock stars, naturally make rock star demands.

While we explore native applications from a development perspective, don't forget that there is one more important point: end users. If you're looking for an app, you can find it in the App Store. If you start running the application, it will start immediately. If you use an application, you get fast performance and a consistent platform look and feel. If your application needs to be updated, it will tell you that it needs to be updated. The native app gives you everything you'd expect from the company that makes the device you're on, as if the application were to use it.

Native applications are typically developed using the integrated development environment (IDE). The IDE provides tools for building, debugging, project management, and versioning, as well as other tools that professional developers need. While iOS and Android apps are developed using different Ides and languages, there are a lot of similarities in the development environment, and there's no need to delve into the differences. In short, what tools are needed for your device, and what tools you use.
You need these tools because native applications are more difficult to develop. Similarly, the development experience required is richer than the other development scenarios, and you can't just clip the copy objective-c and hope it works. Indeed, the technical expertise of the development team is an important consideration. If you're a professional developer, I'm probably already familiar with proven APIs and frameworks, easy-to-implement effects with built-in widgets, or the benefits of putting code in one place. To be honest, this year's skilled native iOS or Android developers, like rock stars, naturally make rock star demands.

An important part of the HTML5 approach to "write once and run everywhere" is that distribution and support are much easier for native applications. Need to develop a revision or add feature features? Once completed, it can be deployed uniformly for all users. In the case of native applications, the development and testing cycles are long, and consumers often have to log in to the store and download new versions to get the latest revisions. Significant limitations lie in offline storage and security, especially for enterprise mobile applications. While you can seemingly implement offline functionality by slowing files on the device, this is not a good solution at all. Although the underlying database may be encrypted, it is not as well delimited as the native key-chain encryption method that protects each application with a developer certificate. In addition, if you start a Web application with a validation mechanism from the desktop, it requires the user to enter logon credentials whenever the application is sent to the background. This is a bad experience for the user. In general, implementing even trivial security measures on native platforms is a complex task for web mobile developers. Therefore, if security is critical, this factor may determine which mobile technology you choose.

The advantages (and disadvantages) of both native and HTML5 hybrid development sets. The hybrid application that we define is a Web application that is built primarily using HTML5 and JavaScript, and then encapsulated in a thin, native container that allows access to native platform functionality through a container.

Comparison of H5, native app and hybrid development