Hybrid App Development Combat

In recent years, as the mobile device type becomes more and more, the operating system becomes more and more, the user's demand is increased, the cost, team member, Technology maturity, time, project requirement and so on can be taken into account before each project starts. As a result, programs to develop apps have become more and more numerous. There was a small wave of HTML5, where countless people participated or saw a discussion: native development or mixed development, or web development? What is the best practice, I think only the practice of the people will know. Especially in this era of mobile internet full of variables.

Analysis of current situation of Hybrid app

Web App

There is no doubt that Web apps are the cheapest and fastest solution. Especially in the last two years very popular response-style design, WEB app Market provides a very good practice venue. The most recent example of a typical web app is the application of sun weather, which is highly praised for its detailed handling.

In general, the following features are a Web App: Run with a browser, a Web front-end architecture, a lot of important mobile features that are inaccessible, such as contacts and push notification; single Page app; sales channels are limited to browsers.

Hybrid App

The so-called hybrid app actually has different branches. And there will be overlap with the native application place. Here are three different solutions.

Scheme I: Use middleware such as PhoneGap, Appcan, take webview as user interface layer, JavaScript as the basic logic, and middleware communication, and then the middleware access to the low-level API, the way of application development. This architecture is generally very dependent on the performance of the WebView layer.

Option two: Use Adobe Air, rubymotion, Appcelerator, or Xamarin, an unofficial language tool, to be packaged into a native application. Why do I define them as hybrid apps, the main reason is that they are not very simple to use native language to develop, but by providing developers with friendly development tools, and the compromise of this development language into the native language, eventually packaged the entire application, so also belong to the mixed application category.

Solution III: Based on the development of native applications, embedded WebView But the overall architecture is provided with native applications, typically such development consists of native developers and Web front-end developers. Native developers will write basic architectures and APIs that allow web developers to develop interfaces and most of the rendering. Guaranteed to the interactive design, as well as the development of a relatively eclectic effect out, optimization will also have a good effect. (The program was used by Facebook Three20)

Therefore, the Hybrid app has the following features:

Development may not adopt or most of the original language is not used, but there are all the characteristics of native applications;

The architecture scheme will differ from the original, which is basically determined by the tools;

has cross-platform characteristics;

General development relative to the way of primary development is simple.

Native App

Native app is undoubtedly the most reliable solution. But the learning cost, the talent cost, the development efficiency as well as takes care of the different platform the characteristic to consider, has become the development person's mind a hurdle. As to say this hurdle is insurmountable or together to let you improve the ridge, I think it depends entirely on yourself. Based on the considerations of various factors, it is estimated that many people will choose a compromise solution to the development of the hybrid app, including the author himself.

More of the following will be discussed around Hybrid app development.

Advantages and disadvantages of Hybrid app in development

In the development process of hybrid app, several different schemes have been experienced by the author. Of course, also experienced the development phase of native app. In such a tangled and complex process to give the author a lot of experience, the following author will also on their own experience and share the pros and cons of these programs. For the beginning of the friend, the author is from the front of the web, after all, low threshold, and can quickly cultivate their confidence and the sense of the code. After that, we started to touch the mobile development. So I'll start with the first program from hybrid app.