AI prompts
base on A curated list of awesome things related to HarmonyOS. 华为鸿蒙操作系统。
[English Docs](README.md) | [中文文档](doc/README-zh.md) | [Türkçe Dökümanlar](doc/README-tr.md)
# HarmonyOS
![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)
<p align="center">
<a href="https://github.com/Awesome-HarmonyOS/HarmonyOS">
<img src="assets/img/hi.jpg" width="750px">
</a>
</p>
> A curated list of awesome things related to HarmonyOS
# Ⅰ . What is HarmonyOS?
`HarmonyOS` is the first full-scene distributed OS based on microkernel. It is an operating system independently developed by Huawei. `HarmonyOS` System was officially released at the Huawei Developers Conference (<HDC.2019>) on August 9, 2019. Huawei will take the lead in deploying intelligent terminals such as smart screens, vehicle terminals and wearable terminals. In the future, more smart devices will be equipped with open source `HarmonyOS` than ever.
`HarmonyOS` achieves modular coupling, which corresponds to flexible deployment of different devices. `HarmonyOS` has three layers of architecture. The first layer is the core, the second layer is the basic services, and the third layer is the program framework. It can be used on a large screen, PC, automobile and other different equipment. It can also be used on mobile phones at any time, but for the time being, Huawei still prefers Android.
The underlying layer of HarmonyOS is composed of `HarmonyOS microkernel`, `Linux kernel` and [`Lite OS`](https://github.com/Awesome-HarmonyOS/HarmonyOS/tree/master/Huawei_LiteOS) and it will become a complete HarmonyOS microkernel architecture in the future.
# Ⅱ . Development process
- [2012] HarmonyOS started out in Shanghai Jiao Tong University in 2012.
- [2018.8.24] Huawei applied for the `Huawei HarmonyOS` trademark. The registration announcement date of `HarmonyOS` trademark is May 14, 2019. The exclusive rights of `HarmonyOS` trademark are from May 14, 2019 to May 13, 2029.
- [2019] Huawei has allegedly shipped 1 million smartphones with its self-developed "HarmonyOS" operating system onboard for testing.
- [2019.5.17] Huawei Operating System Team developed its own proprietary operating system `HarmonyOS`.
- [2019.8.9] Huawei officially released `HarmonyOS`, and `HarmonyOS` Operating System will be open source.
# Ⅲ . Features
![](assets/img/harmony/features.png)
HarmonyOS is designed to meet the high standard connection requirements of full-scene intelligent experience. For this reason, Huawei has proposed four system solutions with major features.
* #### 1. Distributed architecture is first used in the terminal OS to realize seamless collaborative experience across terminals
HarmonyOS's "Distributed OS Architecture" and "Distributed Soft Bus Technology" shield the application developers from the difficulties of implementing the underlying technologies of the corresponding distributed applications through the four capabilities of public communication platform, distributed data management, distributed capability scheduling and virtual peripherals, enabling developers to focus on their own business logic, like open. Developing cross-terminal distributed applications like the same terminal also enables the final consumers to enjoy the seamless experience brought by the powerful cross-terminal business collaboration capability for each use scenario.
![](assets/img/harmony/harmonyos1.jpg)
* #### 2. Determine the time delay engine and high-performance IPC technology to achieve natural fluency in the system
HarmonyOS solves the problem of inadequate performance of existing systems by using two technologies: deterministic delay engine and high-performance IPC. Determining the delay engine can assign priority and time limit of task execution in the system before task execution. The priority task resources will give priority to scheduling, and the application response delay will be reduced by 25.7%. The compact structure of HarmonyOS microkernel greatly improves the performance of IPC (interprocess communication) and the efficiency of process communication is five times higher than that of existing systems.
![](assets/img/harmony/harmonyos2.jpg)
* #### 3. Rebuilding Trusted Security of Terminal Equipment Based on Microkernel Architecture
HarmonyOS adopts a new micro-core design, which has stronger security features and low latency. The basic idea of microkernel design is to simplify the functions of the kernel, to realize as many system services as possible in user states outside the kernel, and to add security protection to each other. Microkernels only provide the most basic services, such as multi-process scheduling and multi-process communication.
![](assets/img/harmony/harmonyos3.jpg)
HarmonyOS applies microkernel technology to Trusted Execution Environment(TEE), and reshapes trusted security through formal methods. A Formal method is an effective means to verify the correctness of the system and the absence of loopholes from the source by using mathematical methods. Traditional verification methods such as function verification and simulation attack can only be validated in limited scenarios, while formal methods can validate all software running paths through the data model. For the first time, HarmonyOS has applied formal methods to terminal TEE, which significantly improves the security level. At the same time, because the code amount of HarmonyOS microkernel is only one-thousandth of that of Linux macro-kernel, its attack probability is greatly reduced.
* #### 4. Through unified IDE to support a single development, multi-terminal deployment, achieve cross-terminal ecological sharing
![](assets/img/harmony/harmonyos4.jpg)
HarmonyOS relies on multi-terminal development IDE, multi-language unified compilation, distributed architecture Kit to provide screen layout control and interactive automatic adaptation, support control dragging, preview-oriented visual programming, so that developers can efficiently build multi-terminal automatic running App based on the same project, to achieve real one-time development, multi-terminal. Deployment to achieve shared ecology across devices. Huawei Ark Compiler is the first static compiler to replace the Android virtual machine model, which allows developers to compile high-level languages into machine code at one time in the development environment. In addition, the Ark Compiler will support multi-language unified compilation in the future, which can greatly improve the development efficiency.
# IV . Resources
## 1. Official Resources
- [Official Site](https://developer.huawei.com)
- [Release Notices]
- [Security Notices]
- [Tutorials]
- [Documentation]
## 2. Download
- [Mirrors]
## 3. Architecture References
- [LiteOS](Huawei_LiteOS/README.md)
- [ABI] Application Binary Interface
- [EABI] Embedded Application Binary Interface
## 4. Hardware drivers
- [Device compatibility]
- [Standards & Protocols]
- [Hareware Quality Specification]
- [Driver Development Kit]
- [Driver Samples]
- [Debugging Tools]
- [Security]
- [5th Gen Drivers and Firmware]
- [Boot and UEFI]
- [ACPI/SoC]
- [Wi-Fi]
- [USB]
- [Printer]
## 5. Developer Tools
#### Compiler
- [Ark] `Harmony` is an Android-app compatible operating system, Ark compiler can improve Android system operation fluency by 24%, response speed by 44%, and the smoothness of the third-party application up to 60%.
#### SDK
[about SDK]
#### IDE
- [LiteOS IDE][Huawei LiteOS Studio](https://static.huaweicloud.com/upload/files/sdk/LiteOS_IDE.zip)
## 6. Community
- [Questions]
## 7. Books
[about books]
## 8. Products
- [Honor Smart Screen -- The first device to use the HarmonyOS](products/honor_smart_screen.md)
## 9. Videos
* [Instructional Videos]
* [Huawei HDC.2019 Harmony OS & EMUI10 Live Record](https://youtu.be/yUVGc7zpuKU)
* [Honor Smart Screen TV Official Trailer](https://youtu.be/GczF2CKIGPk)
Tips: This project is not official. This project collects documents about HarmonyOS from the Internet. This is not a commercial project. This project just introduces HarmonyOS and all documents and codes come from the Internet. If you use this project for business or something about making money, or in the event of any disputes arising from the usage of, or in connection with this project, you will accept all responsibility for the negative results or effects of one's choice or action.
", Assign "at most 3 tags" to the expected json: {"id":"7119","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"