As of June 2020 there were 4.4 millions apps across the App Store and Google Play. Mobile apps are everything nowadays and with the growth of mobile first, they are now the most common way of connecting with your customers. This isn’t just restricted to software itself, but all services, including food delivery, banking, travel and shopping all have apps available on iOS and Android. However, a growing trend spearheaded by the likes of Uber and Instagram have seen the rise of hybrid apps and therefore hybrid development skyrocket.
截至2020年6月 ， App Store和Google Play上有440万个应用程序 。 移动应用已成为当今的一切，随着移动优先发展，它们已成为与客户建立联系的最常见方式。 这不仅限于软件本身，而且所有服务(包括送餐，银行业务，旅行和购物)都可以在iOS和Android上使用应用程序。 然而，由Uber和Instagram等公司带动的增长趋势见证了混合应用程序的兴起，因此混合开发迅猛发展。
Most companies will inevitably ask, “which is better? native or hybrid?” However since both approaches have their own strengths and weaknesses and the very companies asking this question will have their own budget and time constraints, business objectives and sales & marketing strategies; we need to change the question before we can provide some clarity. Rather than “which is better,?” we should instead ask, “which is better for me?”
大多数公司都会不可避免地问：“哪个更好？ 本地还是混合？” 但是，由于两种方法都有其优点和缺点，而提出这个问题的公司也将有自己的预算和时间限制，业务目标以及销售和营销策略； 我们需要先更改问题，然后才能提供一些清晰度。 而不是“哪个更好？” 相反，我们应该问：“哪个对我更好？”
原生VS混合101 (NATIVE VS HYBRID 101)
So you need an app? Great! Now it’s time to assess your options. So what are your options? Well, there are native apps which are purpose built for each operating system, such as iOS and Android and there are hybrid apps which are in essence websites that are designed to be cross-platform functioning. Both are great, but they work in very different ways.
因此，您需要一个应用程序吗？ 大！ 现在是时候评估您的选择了。 那么您有什么选择呢？ 好吧，有专门针对每种操作系统(例如iOS和Android)构建的本机应用程序，还有本质上是旨在跨平台运行的网站的混合应用程序。 两者都很棒，但是它们以不同的方式工作。
Native apps are usually built in Objective C and Swift for iOS and in Java and Kotlin for Android. For hybrid apps, developers will use web technologies such as Javascript frameworks, HTML and CSS. In essence, they are websites packaged into containers that emulate software behaviour for every platform to function and look in a natural way. Hybrid developers deal with a central code that covers both platforms.
本机应用程序通常在iOS的Objective C和Swift中以及在Android的Java和Kotlin中构建。 对于混合应用程序，开发人员将使用Web技术，例如Javascript框架，HTML和CSS。 从本质上讲，它们是包装在容器中的网站，它们模仿软件行为以使每个平台都能正常运行并看起来自然。 混合开发人员处理涵盖两个平台的中央代码。
This means it’s the development process that is the main difference when it comes to comparing native vs hybrid. It is worth noting that visually, it is very hard to tell the difference between the two when comparing end-products.
这意味着开发过程是比较本机与混合的主要区别。 值得一提的是，在比较最终产品时，很难说出两者之间的区别。
At a high level native apps can be characterised by ‘faster’ performance on the whole and ‘better’ security. And to be clear here, by ‘faster’ we’re talking minutely — the two examples above (Instagram and Uber) hardly scream slow and lagging; and by ‘better’ security we’re talking things such as two-factor authentication which can be integrated with native apps — think how transaction authorisation codes are sent via text and auto populated into your banking app — this is a sign its a native app. However, the payoff here is complexity and therefore slower development cycles. Additionally, each platform (iOS and Android) will have its own codebase, which will increase costs in terms of development and maintenance.
从总体上讲，本机应用程序的特点是整体上“更快”的性能和“更好”的安全性。 在这里要明确的是，通过“更快”，我们正在进行细微的交谈-上面的两个示例(Instagram和Uber)几乎没有尖叫缓慢而落后。 通过“更好”的安全性，我们正在谈论可以与本机应用程序集成的两因素身份验证之类的东西-考虑如何通过文本发送交易授权码并将其自动填充到您的银行应用程序中-这是其本机应用程序的标志。 但是，这里的收益是复杂性，因此开发周期较慢。 此外，每个平台(iOS和Android)将拥有自己的代码库，这将增加开发和维护成本。
As for hybrid apps, versatility and adaptability will be the notable advantages that speed up the development process as well as simultaneously reducing cost. The negligibly slower performance will be tiny concession.
对于混合应用程序，多功能性和适应性将是显着的优势，可以加快开发过程并同时降低成本。 可以忽略不计的性能降低是微不足道的。
When comparing the benefits of native vs hybrid its quite clear the bulk of the task for any company is to clarify the purpose of their app from the outset— Specialised native apps containing sensitive information provide functionality to include more stringent security measures so they are widely chosen by financial institutions like banks (see above), insurance companies etc. These companies and therefore their apps attract higher costs for the development and maintenance of the app as a byproduct of stricter security controls. Larger companies do also choose to go down the native route simply because they can afford to do so, Amazon and LinkedIn for example both use native apps when a hybrid option would work just as well.
在比较本机与混合型的优势时，对于任何公司而言，很明显的任务是从一开始就明确其应用程序的目的-包含敏感信息的专业本机应用程序提供了包含更严格安全措施的功能，因此被广泛选择这些公司及其应用程序吸引了银行(见上文)，保险公司等金融机构的注意，因此，作为更严格的安全控制措施的副产品，它们吸引了更高的开发和维护成本。 大型公司也确实选择沿本机路线发展，仅仅是因为他们有能力负担得起，例如，当混合选项同样适用时， 亚马逊和LinkedIn都使用本机应用程序。
The cross-platform hybrid framework is generally catered more towards startups and SMEs with restricted budgets and businesses focused on content delivery. I say generally, as this is by no means a defining feature — This approach is also very well suited to the travel industry and businesses that focus on products and product reviews, photo-sharing and customer ratings. Uber, Instagram, AirBnB and Twitter all built hybrid apps.
跨平台混合框架通常更适合预算有限的初创企业和中小型企业以及专注于内容交付的企业。 我一般地说，因为这绝不是一个定义性功能-这种方法也非常适合专注于产品和产品评论，照片共享和客户评级的旅游行业和企业。 Uber，Instagram， AirBnB和Twitter都构建了混合应用程序。
The decision to go native or hybrid has not caused competition between the two models, its actually unearthed further opportunities for companies to provide their users with better user experiences. Which if you think about it, is only going to benefit the consumer. So let’s dig a little deeper.
决定采用原生或混合模式并没有引起这两种模式之间的竞争，实际上，这为公司提供了进一步的机会，为用户提供更好的用户体验。 如果您考虑一下，那只会使消费者受益。 因此，让我们深入研究。
混合应用程序开发 (HYBRID APP DEVELOPMENT)
In a nutshell a hybrid application is at its core a website that has been put into containers. As such, each one has to use specially designed APIs to reach fundamental features. These apps operate a web view control in order to receive the full-screen JavaScript (JS) and HTML files leveraging the rendering engine of the built-in OS browsers.
简而言之，混合应用程序的核心是已放入容器的网站。 因此，每个人都必须使用专门设计的API来实现基本功能。 这些应用程序运行Web视图控件，以便利用内置OS浏览器的呈现引擎来接收全屏JavaScript(JS)和HTML文件。
用于混合应用程序开发的技术 (Technologies used for hybrid application development)
Most tech companies will use a combination of frameworks to build hybrid apps. The three most popular are:
大多数科技公司将使用多种框架组合来构建混合应用程序。 最受欢迎的三个是：
Ionic — The ‘best’
离子 -“最佳”
The framework of choice by developers, not for any other reason than it is the most familiar. This framework produces mobile applications with standard web technologies such as JavaScript, CSS, HTML, Angular, etc. There are a lot of accessible UI components that are simple to deal with and development time is as great as with all other frameworks for hybrid app examples. In spite of all the benefits, the maintenance might be a tad more difficult. Ionic relies on integrations with lots of plugins, so when issues do present themselves, it may require additional manual adjustments.
开发人员选择的框架，除了最熟悉的原因外，没有其他原因。 此框架使用标准的Web技术(例如JavaScript，CSS，HTML，Angular等)生成移动应用程序。有许多易于访问的UI组件，这些组件易于处理，开发时间与混合应用程序示例的所有其他框架一样长。 。 尽管有所有好处，维护可能会更加困难。 Ionic依赖于与许多插件的集成，因此当出现问题时，可能需要进行其他手动调整。
Some high level benefits of Ionic are:
Ionic的一些高级好处是：
- It’s Angular-based so no additional language is required 它基于Angular，因此不需要其他语言
- It has an expansive and rich collection of powerful features 它具有丰富而丰富的强大功能集合
- Out of the box it has plenty of UI components and predefined elements 开箱即用，它具有大量的UI组件和预定义的元素
- There a built-in dev server 有一个内置的开发服务器
- It has a live reload system and app enabling you to preview your hybrid app right on your target device 它具有实时重新加载系统和应用程序，可让您直接在目标设备上预览混合应用程序
- It has a large dev community 它有一个庞大的开发社区
- Debugging tools are included 包含调试工具
- It comes with a command-line interface that streamlines the dev cycle of your Node.js and TypeScript apps 它带有一个命令行界面，可简化Node.js和TypeScript应用程序的开发周期
React Native — The favourite
React Native —最喜欢的
Facebook’s open-source technology for cross-platform compatibility and the developers favourite. The simplified UIs have considerably increased performance, specifically reloading. React Native is mostly utilised because of the short development time and the fact that developers who are already fluent in React can pick this up instantly. The software engineers have access to ready-to-apply units, however, the framework might lack certain components. Both Facebook and the wider dev community regularly provide updates.
Facebook的跨平台兼容性开源技术和开发人员的最爱。 简化的UI大大提高了性能，特别是重新加载。 由于开发时间短，而且已经精通React的开发人员可以立即使用React Native，因此主要使用React Native。 软件工程师可以访问随时可以应用的单元，但是，该框架可能缺少某些组件。 Facebook和更广泛的开发人员社区都定期提供更新。
Some high level benefits of React Native are:
React Native的一些高级好处是：
- A much shorter app dev cycle 更短的应用程序开发周期
- Has a large community of developers 有大量的开发人员社区
- It’s high-powered: rendered with native code 它功能强大：使用本机代码呈现
- Costs can be further reduced by reusing code 重用代码可以进一步降低成本
- It offers a variety of plugins: display grid picture, feed, etc. 它提供了多种插件：显示网格图片，提要等。
- It’s Node.js supported 支持Node.js
- It features live reload with 2 different screens: to update your code and to preview those updates in real-time 它具有通过2个不同的屏幕进行实时重新加载的功能：更新代码并实时预览这些更新
Flutter — The newcomer
Flutter —新人
Google’s foray into the hybrid framework space. Although relatively new, as a Google product it stands a good chance of competing with the big boys. Flutter has differentiated itself as the go-to choice when you wish to create a visually impressive MVP fast. Speed is everything for Google. Its flexible design components allow you to pull a visual masterpiece of an application together and really provide a solid user experience. With Flutter you get a powerful toolkit to develop and run a cross-platform app in no time. Plus, it’s designed to support numerous languages and run smoothly across several platforms. All without the need to look for an alternative for Java, Swift or Objective C.
Google进军混合框架领域。 尽管相对较新，但作为Google产品，它很有可能与大公司竞争。 当您希望快速创建视觉上令人印象深刻的MVP时，Flutter已经成为了首选产品。 速度对Google至关重要。 其灵活的设计组件使您可以将应用程序的视觉杰作组合在一起，并真正提供扎实的用户体验。 借助Flutter，您将获得功能强大的工具包，可以立即开发和运行跨平台应用程序。 另外，它旨在支持多种语言，并且可以在多个平台上平稳运行。 所有这些都无需寻找Java，Swift或Objective C的替代方案。
Some high level benefits of Flutter are:
Flutter的一些高级好处是：
- It’s incredibly fast 快得惊人
- It comes with a hot reload feature 它具有热重载功能
- It provides CLI and VI editors 它提供CLI和VI编辑器
- Own widgets: one click insert buttons, sliders, switches, dialog boxes etc 自己的小部件：一键插入按钮，滑块，开关，对话框等
- There functionality to to assemble and nest multiple widgets for app UI 可以为应用程序UI组装和嵌套多个小部件的功能
所以总结：混合动力的优势 (So to round up: The Advantages Of Hybrid)
Single code base — This is the single most important advantage and the one that facilitates all others. Hybrid apps are preferred by companies and developers as they can perform on both platforms. There is no need to build two separate code bases for iOS and Android.
单一代码库 —这是最重要的单一优势，并且可以促进所有其他优势。 公司和开发人员首选混合应用程序，因为它们可以在两个平台上执行。 无需为iOS和Android构建两个单独的代码库。
Lower cost — Huge savings can be achieved by developing one mobile application while addressing users on across platforms. Whether developing in-house or via an agency or consultancy, you will only have to hire one team with web development expertise. This results in a wider talent pool to chose from and a lower overall cost to build and maintain.
更低的成本-通过开发一个移动应用程序同时满足跨平台用户的需求，可以节省大量资金。 无论是内部开发，还是通过代理机构或咨询公司进行开发，您都只需雇用一支具有Web开发专业知识的团队。 这样可以提供更多的人才库供选择，并且降低了构建和维护的总体成本。
Ease to build — You will reach your end product faster. You dev team will not have to deal with each platform separately, the code is created once and testing time is also greatly reduced.
易于构建 -您将更快地获得最终产品。 您的开发团队将不必分别处理每个平台，代码只需创建一次，并且测试时间也大大减少。
Faster delivery time — Similar to the above, there is no need for an iOS and Android team or a large cross-functional team, you can build your product with one relatively small team of developers.
更快的交付时间 —与上述类似，不需要iOS和Android团队或庞大的跨职能团队，您可以由一个相对较小的开发人员团队来构建产品。
Ease of maintenance — All required changes and updates will be maintained simultaneously on both platforms. This is not only convenient for the developers but for your users as well. A lot of known issues can be addresses server side, resulting in your users just being pushed the updates automatically.
易于维护 —所有必需的更改和更新将在两个平台上同时维护。 这不仅对开发人员很方便，对您的用户也很方便。 许多已知问题可能是服务器端地址，导致您的用户被自动推送更新。
混合动力的缺点 (Disadvantages Of Hybrid)
Offline mode — By the very nature of their design hybrid apps require a regular and stable internet connection. Some functionality will not be available when the user loses connection. This is slowly changing, but it is still a widely considered disadvantage of hybrid over native.
离线模式 -本质上，混合应用程序需要常规且稳定的Internet连接。 用户断开连接后，某些功能将不可用。 这种情况正在慢慢改变，但仍然被广泛认为是混合动力比原生动力的劣势。
Plugin restriction — These cross-platform frameworks are reliant on plugins to be connected with the device features. If the desired plugin is not available or does not exist, developers will have to manually create them to produce a function this can add unforeseen cost and increases delivery time.
插件限制 -这些跨平台框架依赖于要与设备功能连接的插件。 如果所需的插件不可用或不存在，开发人员将必须手动创建它们才能产生功能，这会增加无法预料的成本并增加交付时间。
Let’s jump over to Native now.
现在让我们跳到Native。
原生应用开发 (NATIVE APP DEVELOPMENT)
Native apps are built for a single platform and use very different technologies. For Apple and iOS, Objective C and Swift are used and for Google and Android, it’s Java or Kotin. Companies that usually choose the native route have the complexity of employing two teams to build two products to run on two platforms simultaneously. Thankfully it does not take a rocket scientist (or a developer) to work out that the development process is therefore longer and more costly as a result. However, for certain applications that utilise the mobile hardware itself such as in-built step counters, or host user and financially sensitive data — the final result of a native app balances out this additional cost. In the end for these types of products, the customers are presented with a more responsive and faster experience. Now whilst your choices might be limited, it is still important to understand the frameworks used across both iOS and Android.
本机应用程序是为单个平台构建的，并且使用非常不同的技术。 对于Apple和iOS，使用Objective C和Swift；对于Google和Android，使用Java或Kotin。 通常选择本地路线的公司具有聘请两个团队来构建两个产品以同时在两个平台上运行的复杂性。 幸运的是，不需要火箭科学家(或开发人员)就可以得出开发过程因此更长，成本更高的结论。 但是，对于某些利用移动硬件本身的应用程序(例如内置计步器或主机用户和财务敏感数据)，本机应用程序的最终结果可以抵消这笔额外费用。 最后，对于这些类型的产品，将为客户提供更快速响应的体验。 现在，尽管您的选择可能受到限制，但了解跨iOS和Android使用的框架仍然很重要。
iOS本机应用程序开发技术 (Technologies for iOS native application development)
This programming language is time tested and known for its great development experience, accessible & rich libraries and a vast pool of technical experts. Objective-C is a mature framework, which is cross compatible with other programming technologies. However, new languages are constantly appearing and often Objective C does not have the ability to support all the latest features.
这种编程语言经过了时间的考验，并以其丰富的开发经验，可访问且丰富的库以及大量的技术专家而闻名。 Objective-C是一个成熟的框架，可与其他编程技术交叉兼容。 但是，新的语言不断出现，并且Objective C通常不具备支持所有最新功能的能力。
Relatively new, compared to Objective C — Swift is a programming framework introduced by Apple that has become the favoured alternative for building iOS native apps. Developers have been quick to point out that it’s quicker and easier to learn as well as work with. It’s also constantly developing that’s why at any given time it may lack some components. However, it has been said that Swift might replace Objective-C entirely in the near future.
与Objective C相比，它是相对较新的-Swift是Apple引入的编程框架，已成为构建iOS本机应用程序的首选替代方法。 开发人员很快就指出，它更容易学习和使用。 它也在不断发展，这就是为什么在任何时候它都可能缺少某些组件的原因。 但是，有人说Swift可能会在不久的将来完全取代Objective-C。
Android固有的技术 (Technologies native to Android)
The primary programming language for Android mobile applications is Java. In fact many desktop and web development products are also based on Java. It has become a special system of tools that provide developers with an almost unlimited library. It helps to simplify the overall programming process. However, applications on Java require more memory and perform slower compared to other frameworks.
Android移动应用程序的主要编程语言是Java。 实际上，许多桌面和Web开发产品也都基于Java。 它已成为一种特殊的工具系统，可为开发人员提供几乎无限的库。 它有助于简化整个编程过程。 但是，与其他框架相比，Java上的应用程序需要更多的内存，并且执行速度较慢。
It is a programming language specifically developed to work with Java and Java Virtual Machine. Because of that, its usage is supported and approved by Google for the development of Android applications. One of the main advantages of Kotlin over regular Java is that its type interface allows working to be done using a shorter syntax. This fact reduces the programming time to make an application for Android. Now it is included as an alternative to the standard Java compiler for the Android Studio. Expedia and Pinterest are some examples of companies that use Kotlin for their Android apps.
它是专门为与Java和Java虚拟机一起使用而开发的一种编程语言。 因此，它的使用得到Google支持并批准用于开发Android应用程序。 Kotlin与常规Java相比的主要优点之一是其类型接口允许使用较短的语法完成工作。 这个事实减少了为Android制作应用程序的编程时间。 现在，它已包括在内，以替代Android Studio的标准Java编译器。 Expedia和Pinterest是将Kotlin用于其Android应用的公司的一些示例。
综述：本地人的优势 (Rounding up: Advantages Of Native)
Better performance — When compared, native performance will always be faster as the applications are built with a framework that is native to the platform.
更好的性能 -与之相比，由于应用程序是使用平台本地框架构建的，因此本地性能将始终更快。
Data security — It is much easier to make a native application secure. This is usually the most important advantage of native apps and is why a a lot of companies are interested in providing it via this approach for their customers especially sectors dealing with sensitive data such as in finance.
数据安全性 -使本机应用程序安全很容易。 这通常是本机应用程序最重要的优势，这就是为什么很多公司都希望通过这种方法向其客户提供它的原因，特别是在处理敏感数据(例如金融)的领域。
General functionality — The app will have the important ability to connect the device hardware features and different databases. There is no need for plugins or extra tools.
常规功能 -该应用将具有连接设备硬件功能和不同数据库的重要功能。 无需插件或其他工具。
Comprehension — The developers are already aware of all the strengths and weaknesses of using well-established technologies. They will help to find the right approach for receiving final desirable results.
理解力 -开发人员已经意识到使用成熟技术的所有优点和缺点。 他们将帮助找到正确的方法来获得最终的理想结果。
本地人的缺点 (Disadvantages Of Native)
It’s worth noting that some of the disadvantages listed below depend on which platform you choose to develop for.
值得注意的是，下面列出的一些缺点取决于您选择要开发的平台。
Time consuming and costly — It requires time to build complex software. Couple this with the distribution of users across two main platforms and this doubles the amount of work and testing needed to keep two separate applications for both iOS and Android up and running.
耗时且成本高昂 -构建复杂的软件需要时间。 再加上在两个主要平台上的用户分布，这可以使保持两个独立的iOS和Android应用程序正常运行所需的工作量和测试量加倍。
Distributed codebase — Having some features unavailable for iOS or Android is an infamous and still ongoing practice. This happens largely due to limitations in budget or restrictions of the platform. Sometimes, applications in the App Store can be abandoned for years while the Android version receives regular updates and vice versa. Contrast this to hybrid where developers are encouraged to continually push updates in UI and features to the live application on both operational systems.
分布式代码库 —某些臭名昭著且仍在持续的做法是使某些功能不适用于iOS或Android。 发生这种情况的主要原因是预算限制或平台限制。 有时，App Store中的应用程序可能会被丢弃多年，而Android版本会定期进行更新，反之亦然。 与此形成对比的是混合驱动程序，鼓励开发人员将UI和功能的更新不断推送到两个操作系统上的实时应用程序。
所以，哪个更好？ (SO, WHICH IS BETTER ???)
Pros and cons aside, its about understanding yourself. Answering this will single-handedly help shape your approach to implementation. So to understand yourself, you must address some key points.
除了利弊外，它还可以帮助您了解自己。 回答这一问题将单方面帮助您塑造实施方法。 因此，要了解自己，您必须解决一些关键点。
First of all, determine your audience and what service you provide. If the app is content-oriented, a cross-platform framework and therefore a hybrid app will be a suitable choice. If your app deals with financially sensitive data, it’s probably better to go native.
首先， 确定您的受众以及您提供的服务 。 如果该应用程序是面向内容的，那么跨平台框架以及混合应用程序将是合适的选择。 如果您的应用程序处理财务敏感数据，则最好采用本机模式。
Secondly, in terms of the performance differences, as mentioned right at the top — these are negligible. Hybrid frameworks are continually improving and are very much keeping pace with native apps.
其次， 就性能差异而言 (如顶部所述)， 这些 差异 可以忽略不计 。 混合框架不断改进，并且与本机应用程序保持同步。
Thirdly, define your budget. Hybrid apps cost less and are less time consuming to build. You don’t need two separate teams for Android and iOS working on what is essentially two different apps.
第三， 定义预算 。 混合应用成本更低，构建时间也更少。 您基本上不需要两个独立的Android和iOS团队来开发本质上是两个不同的应用程序。
Lastly, in terms maintenance, it’s generally easier to manage one mobile app as opposed to two native apps. And if you’re employing a team, the talent pool is relatively cheaper (and deeper) for web developers than it is for native app developers.
最后，在维护方面， 与两个本机应用程序相比，管理一个移动应用程序通常更容易。 而且，如果您正在雇用一个团队，则与本地应用程序开发人员相比，Web开发人员的人才库相对便宜(而且更深入)。
So, with all that in mind, hybrid or native? Well, it should be clear by now it’s really not that simple. It does genuinely comes down to what the purpose of your app is, what audience you are appealing to and what your budget is. Once you have answered all of these, that will steer you to which approach serves you better.
那么，考虑到所有这些，混合还是本地？ 好吧，现在应该很清楚，它真的不是那么简单。 确实，这确实取决于您的应用程序的用途，所吸引的受众以及您的预算是多少。 一旦您回答了所有这些问题，这将引导您采用哪种方法更好地为您服务。
翻译自: https://medium.com/swlh/hybrid-vs-native-apps-and-how-to-choose-1d1ed0350fe8
4万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
