Differentiated advantages of hybrid development for web development native development

Recently, some people are talking about whether native development is good or mixed development, the following is a reference to the data:

Recent native apps, Web apps, and hybrid apps have made us more familiar with the names, and now we'll take a closer look at the differences between the pros and cons of various applications.

First, the native application

Have you ever used Microsoft PowerPoint or Word? These can be run directly on your computer or on a smartphone, and simply, native apps are developed specifically for an operating system, such as iOS, Android, BlackBerry, and so on, which are running on their own mobile devices.

Advantages:

• Access to all functions of the phone (GPS, camera);
• Faster, high performance, good overall user experience;
• can be used offline (because it is used on a platform relative to the web);
• Supports a large number of graphics and animations; Easy to find (inside the App Store) and rediscover (app icon will always be on the homepage);
• App downloads can make a profit (of course, the App Store pulls 20-30% revenue).

Disadvantages:

• High development cost;
• The support device is very limited (usually which system is used on which platform-specific device);
• Online time is uncertain (App store review process varies);
• Content Restrictions (APP store restrictions);
• You will need to re-download the app updates when you get a new version.

For example: Yellow Pages Group has developed several versions (IOS, BlackBerry, Android) that have shelves in every native app market.

Second, the WEB application

Web applications are essentially web-based applications designed for mobile browsers that are developed in a common web development language and can be run on a variety of smartphone browsers.

Advantages:

• Wide range of support equipment;
• low cost of development;
• can be launched immediately;
• no content restrictions;
• Users can use the latest version directly (Automatic Updates without user manual updates).

Disadvantages:

• Slightly poor performance (the requirements for networking are relatively large);
• The user experience is not so flashy;
• Image and animation support is not high;
• Unable to download in the App Store and not be able to get profitable opportunities through app downloads;
• Require networking;
• There are restrictions on mobile phone features (camera, GPS, etc.).

For these shortcomings, if you can use the advantages of HTML 5 on the Web, it will be greatly improved, although the technology is improving, it is not yet able to do everything native application can do.

Some companies, such as the Financial Times, have developed Web applications after native applications, and users have access to their apps via a browser, because their apps take in-app purchases, and the App Store doesn't allow in-app purchases, or they can't get the 20%-30%.

Three, mixed application

Hybrid applications are known to be a combination of native and Web applications that are part of a native app, and that are parts of a Web application, so they must be run partially on the device and partially on the web.

However, the proportion of mixed applications is very free, such as the web accounted for 90%, native accounted for 10%, or 50% per cent.

Advantages:

• Compatible with multi-platform;
• Smooth access to various functions of the mobile phone;
• Downloadable in the App Store (Wen applications apply to native application enclosures);
• Can be used under the line.

Disadvantages:

• Uncertain on-line time;
• User experience is inferior to local application;
• Slightly slower performance (requires network connection);
• Technology is not very mature yet.

Facebook, for example, is a hybrid app that can be used in many app stores, but with a lot of web features, it runs slower, and now it's decided to use native apps to improve performance FB.

Differentiated advantages of hybrid development for web development native development