# harmony-os Published articles for harmony-os. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Huawei's HarmonyOS Next could matter for small computing devices DevFeed: [Why Huawei's HarmonyOS Next could matter for small computing devices]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-04-03T08:46:50Z Content type: opinion Language: en Sources: [Snapp Mobile - Medium]() Topics: [Operating system](), [huawei](), [Open Source](), [Microcontrollers](), [Robotics]() Tags: [harmony-os](), [huawei](), [microcontrollers](), [mobile-app-development](), [open-source](), [operating-systems](), [os](), [robotics]() ### AI overview This opinion article examines Huawei's HarmonyOS Next, a version of HarmonyOS without Android support, and argues that an operating system designed for small computing devices could have a valuable role as those devices become more widespread. ### Source excerpt Last year Huawei ditched Android and in 2025 will be releasing more and more devices running its HarmonyOS Next software platform. HarmonyOS is based on an open source operating system (OpenHarmony) that started as an R&D project at Huawei in 2012. The operating system has been architected to support a wide array of small computing devices from microcontrollers to tablets. It is already used in several of Huawei's TVs, wearables and wireless router products. In 2024 a 'pure' version of the OS, without Android support, was released. This has been branded HarmonyOS Next. Several questions leap to mind: 1/ Does the world actually need a new OS? 2/ Why should we care about what Huawei is doing -- especially those of us outside China? 3/ Finally, what are the chances of success for a new OS? Let's look a little deeper into these topics and try to understand what's going on in this space. 1/ Does the world need a new OS? YES Let me explain why I have come to this conclusion. Computing needs have changed We have seen a steady growth of small form factor computing. We carry computing devices in our pockets, they are found in devices throughout our homes, they are part of our vehicles, they are in medical devices, and in countless industrial settings. Within this context, one could argue that phones are at the larger end of the spectrum when it comes to small computing devices. Single board computers and microcontrollers can be found in mechanical keyboards, security cameras, hand-held medical equipment, at the checkout in our shops etc. Going further, it's not a huge leap to see that the field of robotics is due to take off with the advent of AI for real time context-aware decision making. My first argument, therefore, is that an operating system specifically designed for small computing devices will have a valuable role to play. (Neither iOS nor Android were designed or have evolved to address this need.) Innovation and competition are good Several operating system innovati ## HarmonyOS App Development 101 DevFeed: [HarmonyOS App Development 101]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-01-18T23:23:13Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [App](), [Development](), [ide](), [huawei](), [SDK](), [Tooling](), [jetbrains](), [Package Management](), [Testing](), [Open Source]() Tags: [android](), [app](), [app-development](), [apps](), [code-completion](), [debug](), [deployment](), [development](), [harmony-os](), [huawei](), [ide](), [jetbrains](), [open-source](), [package-management](), [programming-languages](), [refactoring](), [sdk](), [testing](), [tools](), [ui](), [ui-framework]() ### AI overview An overview of HarmonyOS Next app development, covering the Huawei-based DevEco Studio IDE, project configuration, SDK versions, modules, and common development features. The article also outlines programming languages, UI frameworks, build tools, package management, execution, debugging, testing, and profiling. ### Source excerpt Huawei have taken a big step in moving away from the Android platform with the launch of new devices running HarmonyOS Next. This is a brand new operating system that had been design specifically for devices. This means it is lightweight, supports a range of device types, is modular and extensible. In this article we aim to give you an overview of what is available to developers wishing to build apps on this new platform. To that end, we will be looking at the following topics: The IDE Programming Languages UI Framework Build Tools Package Management Running code (devices/emulators) Debugging Testing Profiling Other cool stuff If you are curious about the Harmony platform, its Open Source foundations (OpenHarmony) and its global reach (Oniro), we have written about it here. The IDE The development environment for Harmony apps is currently a Huawei-based IDE which is based on the JetBrains IDE platform. The good news is that JetBrains offers a world-class IDE platform and it makes for a very solid development experience for Harmony apps. For those, wanting to keep to the Open Source side of Harmony (OpenHarmony and Oniro), you are out of luck right now. DevEco Studio is proprietary, albeit free to use software. Let's look at a couple of IDE features -- these should not surprise you but hopefully demonstrates that the platform is already in a good place (as far as IDEs go). Project Creation Creating a project will look familiar already for many. There are a few project templates to choose from to bootstrap your project. New Project Templates You will also then need to configure a couple of options -- a couple of notes on these (which could probably be expanded into a separate article). Firstly, the bundle name is used for app signing and identity. Secondly, an app supports a single SDK version. (The latest SDK version is 13, however version 11 is still widely used.) Thirdly we can specify the module name. The default ('entry') isn't very descriptive. If you have a singl ## CI CD for OpenHarmony Project -- GitHub Action DevFeed: [CI CD for OpenHarmony Project -- GitHub Action]() Original publisher: [Read original article]() Author: Payam Zahedi Published: 2024-12-09T12:05:48Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [GitHub Actions](), [CI/CD](), [GitHub](), [Development]() Tags: [ark-ts](), [build](), [building](), [ci-cd](), [ci-cd-pipeline](), [ci-cd-workflows](), [github](), [github-action](), [github-actions](), [harmony-os](), [open-harmony](), [sdk](), [testing](), [verify]() ### AI overview This tutorial explains how to create a GitHub Actions CI/CD workflow for building and verifying an OpenHarmony application. It introduces the roles of DevEco Studio, Hvigor, OHPM, the OpenHarmony Code Linter, and the reusable oh-action for preparing the required SDK and command-line tools. ### Source excerpt CI CD for OpenHarmony Project -- GitHub Action When developing OpenHarmony, we typically use DevEco Studio to write our code, build the project, test it, and run it on our devices, with DevEco Studio taking care of everything under the hood. However, as engineers, we love to automate repetitive processes, right? This is where CI/CD workflows become incredibly useful. GitHub Actions, in particular, is a popular and highly customizable workflow solution. In this article, we'll explore how to create a workflow on GitHub Actions to build and verify our OpenHarmony application. A Little Context To write our GitHub Action workflow, we first need to understand how DevEco Studio works under the hood. Specifically, what tools does it install, and how are they used? In this article, we won't dive too deep into all OpenHarmony tools and DevEco Studio capabilities. Instead, we'll provide a brief overview to understand the components needed for our workflow. hvigorw Hvigor is a simple build tool, much like Gradle for Android, but designed specifically for OpenHarmony apps. It helps you manage tasks, dependencies, and builds easily. DevEco Studio uses hvigorw to build, test, and run apps on devices. ohpm OHPM (OpenHarmony Package Manager) is akin to npm for JavaScript, but tailored for OpenHarmony applications. It helps facilitate the publishing, installation, and management of dependencies for shared packages. DevEco Studio uses OHPM to manage third-party libraries within OpenHarmony projects. Code Linter OpenHarmony's Code Linter is a tool that checks ArkTS and TypeScript code for best practices and coding standards. It helps developers identify and fix issues during development, ensuring high-quality code. Now that we have a good understanding of the tools involved, the next step is to bring these components together into a cohesive GitHub Action that can automate our workflow. This is where oh-action steps in. GitHub - Snapp-Mobile/oh-action: The oh-action is a GitHub Action t