<tdclass="cellrowborder"valign="top"width="49.99%"headers="mcps1.1.4.1.3 "><pid="p54625885713"><aname="p54625885713"></a><aname="p54625885713"></a>SDK for JS.</p>
<tdclass="cellrowborder"valign="top"width="49.99%"headers="mcps1.1.4.1.3 "><pid="p7471158105711"><aname="p7471158105711"></a><aname="p7471158105711"></a>Includes compiling, packaging, signing, database management, and other tools that are required to develop OpenHarmony apps.</p>
<tdclass="cellrowborder"valign="top"headers="mcps1.1.4.1.2 "><pid="p1238951018"><aname="p1238951018"></a><aname="p1238951018"></a>OpenHarmony app previewer, which can be used to view the UI layout during app development.</p>
</td>
</tr>
</tbody>
</table>
1. Open DevEco Studio. If this is the first time you are using it, select **Do not import settings** and click **OK**.
1. Open DevEco Studio. If this is the first time you are using it, select **Do not import settings** and click **OK**.
2. Follow the wizard to set **npm registry**. DevEco Studio has been preconfigured with the corresponding registry. Click **Start using DevEco Studio** to go to the next step.
2. Follow the wizard to set **npm registry**. DevEco Studio has been preconfigured with the corresponding registry. Click **Start using DevEco Studio** to go to the next step.
> If the **Set up HTTP Proxy** page is displayed, it indicates that your network requires a proxy. In this case, set up the DevEco Studio proxy, npm proxy, and Gradle proxy according to [References](#references), and then download the OpenHarmony SDK.
>If the **Set up HTTP Proxy** page is displayed, it indicates that your network requires a proxy. In this case, set up the DevEco Studio proxy, npm proxy, and Gradle proxy according to [References](#section0384143616409), and then download the OpenHarmony SDK.
3. Follow the wizard to download the SDK. By default, the OpenHarmony SDK will be downloaded. You can download the SDK to the default **user** directory or a local path that does not contain any Chinese characters. Then click **Next**.
3. Follow the wizard to download the SDK. By default, the OpenHarmony SDK will be downloaded. You can download the SDK to the default **user** directory or a local path that does not contain any Chinese characters. Then click **Next**.
> If you are not using DevEco Studio for the first time, the SDK download page may not be displayed. In this case, go to **Configure** (or ) > **Settings** > **SDK Manager** > **OpenHarmony SDK** and click **OpenHarmony SDK Location** to download the SDK.
>If you are not using DevEco Studio for the first time, the SDK download page may not be displayed. In this case, go to **Configure** \(or \) \> **Settings** \> **SDK Manager** \> **OpenHarmony SDK** and click **OpenHarmony SDK Location** to download the SDK.
4. On the **Settings Confirmation** page, click **Next**. When the **License Agreement** dialog box appears, click **Accept**.
4. On the **Settings Confirmation** page, click **Next**. When the **License Agreement** dialog box appears, click **Accept**.
Setting up the development environment requires that your network can directly access the Internet.
Setting up the development environment requires that your network can directly access the Internet.
...
@@ -60,103 +89,96 @@ Generally, only some enterprise networks rather than personal area networks or h
...
@@ -60,103 +89,96 @@ Generally, only some enterprise networks rather than personal area networks or h
If you are using DevEco Studio for the first time and the **Set up HTTP Proxy** page is displayed, it indicates that your network requires a proxy. In this case, set up the DevEco Studio proxy, npm proxy, and Gradle proxy.
If you are using DevEco Studio for the first time and the **Set up HTTP Proxy** page is displayed, it indicates that your network requires a proxy. In this case, set up the DevEco Studio proxy, npm proxy, and Gradle proxy.
>If this is not the first time you are using DevEco Studio:
> - On the welcome page, choose **Configure** (or )** > Settings > Appearance & Behavior > System Settings > HTTP Proxy** to access the HTTP Proxy settings. (For macOS, choose **Configure > Preferences > Appearance & Behavior > System Settings > HTTP Proxy**.)
>- On the welcome page, choose **Configure** \(or \)** \> Settings \> Appearance & Behavior \> System Settings \> HTTP Proxy** to access the HTTP Proxy settings. \(For macOS, choose **Configure \> Preferences \> Appearance & Behavior \> System Settings \> HTTP Proxy**.\)
>
>- When on a project page, choose **File \> Settings \> Appearance & Behavior \> System Settings \> HTTP Proxy** to access the HTTP Proxy settings. \(For macOS, choose **DevEco Studio \> Preferences \> Appearance & Behavior \> System Settings \> HTTP Proxy**.\)
> - When on a project page, choose **File > Settings > Appearance & Behavior > System Settings > HTTP Proxy** to access the HTTP Proxy settings. (For macOS, choose **DevEco Studio > Preferences > Appearance & Behavior > System Settings > HTTP Proxy**.)
- **HTTP** parameters: **If you are not sure about the information, contact your network administrator.**
- **HTTP** parameters: **If you are not sure about the information, contact your network administrator.**
- **Host name**: Enter the host name or IP address of the proxy server.
- **Host name**: Enter the host name or IP address of the proxy server.
- **Port number**: Enter the port number of the proxy server.
- **Port number**: Enter the port number of the proxy server.
-**No proxy for**: Enter the URLs or IP addresses which the PC can directly connect to without a proxy server. Use commas (,) to separate URLs and IP addresses.
- **No proxy for**: Enter the URLs or IP addresses which the PC can directly connect to without a proxy server. Use commas \(,\) to separate URLs and IP addresses.
- **Proxy authentication** parameters: Set the parameters only when the proxy server requires authentication.
- **Proxy authentication** parameters: Set the parameters only when the proxy server requires authentication.
- **Login**: Enter the user name used to access the proxy server.
- **Login**: Enter the user name used to access the proxy server.
- **Password**: Enter the password used to access the proxy server.
- **Password**: Enter the password used to access the proxy server.
- **Remember**: Select this option to remember the password.
- **Remember**: Select this option to remember the password.
2. When you have finished, click **Check connection** and enter a URL to check the network connectivity. If the message "Connection successful" is displayed, it indicates that the proxy was set up successfully.
2. When you have finished, click **Check connection** and enter a URL to check the network connectivity. If the message "Connection successful" is displayed, it indicates that the proxy was set up successfully.
3. Click **Next: Configure npm** to set up the npm proxy. For details, see [Setting Up the npm Proxy](#section19984059114316).
3. Click **Next: Configure npm** to set up the npm proxy. For details, see [Setting Up the npm Proxy](#setting-up-the-npm-proxy).
### Setting Up the npm Proxy<a name="section19984059114316"></a>
### Setting Up the npm Proxy
Follow the configuration wizard of DevEco Studio to configure the npm proxy information, which will be written into the **.npmrc** file in the **users/**_user name_ directory.
Follow the configuration wizard of DevEco Studio to configure the npm proxy information, which will be written into the **.npmrc** file in the **users/**_user name_ directory.
> The configuration wizard is displayed only the first time you install DevEco Studio. If the wizard is not displayed, manually add the proxy information to the **.npmrc** file in the **users/**_user name_ directory.
-**npm registry**: Set the address of the npm registry. You are advised to select this option.
>The configuration wizard is displayed only the first time you install DevEco Studio. If the wizard is not displayed, manually add the proxy information to the **.npmrc** file in the **users/**_user name_ directory.
-**npm registry**: Set the address of the npm registry. You are advised to select this option.
-**HTTP proxy**: Proxy server information. By default, the value is the same as that of **HTTP proxy** of DevEco Studio.
-**HTTP proxy**: Proxy server information. By default, the value is the same as that of **HTTP proxy** of DevEco Studio.
-**Enable Https Proxy**: Indicates whether to configure HTTPS proxy. You are advised to select this option.
-**Enable Https Proxy**: Indicates whether to configure HTTPS proxy. You are advised to select this option.
If your proxy server requires the user name and password for authentication, set the user name and password as follows. If your proxy server does not require authentication, skip this step and follow the instructions in [Configuring the SDK Information](#configuring-the-sdk-information).
If your proxy server requires the user name and password for authentication, set the user name and password as follows. If your proxy server does not require authentication, skip this step and follow the instructions in [Configuring the SDK Information](#section1265592425017).
1. Go to the **Users** directory and open the **.npmrc** file.
1. Go to the **Users** directory and open the **.npmrc** file.
2. Modify the npm proxy information. Add the **user** and **password** fields to **proxy** and **https-proxy**. Note that the values may vary depending on the proxy. The following is an example:
2. Modify the npm proxy information. Add the **user** and **password** fields to **proxy** and **https-proxy**. Note that the values may vary depending on the proxy. The following is an example:
> If the password contains special characters, such as \@, \#, and \*, the configuration may not take effect. You are advised to replace the special characters with ASCII codes and add "%" before the ASCII codes. Refer to the following for the mapping between common symbols and ASCII codes.
>If the password contains special characters, such as @, \#, and \*, the configuration may not take effect. You are advised to replace the special characters with ASCII codes and add "%" before the ASCII codes. Refer to the following for the mapping between common symbols and ASCII codes.
>
>- !: %21
> - !: %21
>- @: %40
>
>- \#: %23
> - \@: %40
>- ¥: %24
>
>- &: %26
> - \#: %23
>- \*: %2A
>
> - ¥: %24
>
> - &: %26
>
> - \*: %2A
3. After the proxy is configured, open the CLI and run the following command to check whether the network is normal.
3. After the proxy is configured, open the CLI and run the following command to check whether the network is normal.
```
```
npm info express
npm info express
```
```
If the following information is displayed after running the command, it indicates that the proxy has been set up successfully.
If the following information is displayed after running the command, it indicates that the proxy has been set up successfully.
>Before creating a **.gradle** folder in macOS, set the system to show hidden files.
3. Open the **.gradle** folder, create a **gradle** file, and change the file name extension to .properties.
4. Add the following script to the **gradle.properties** file and save the file:
Modify the host name, port number, user name, password, and proxy exceptions \(**nonProxyHosts**\) based on the actual condition. Separate values for **nonProxyHosts** with a vertical bar \(|\).
4. Add the following script to the “gradle.properties“ file and save the file:
Modify the host name, port number, user name, password, and proxy exceptions (nonProxyHosts) based on the actual condition. Separate values for nonProxyHosts with a vertical bar (|).
```
```
systemProp.http.proxyHost=proxy.server.com
systemProp.http.proxyHost=proxy.server.com
systemProp.http.proxyPort=8080
systemProp.http.proxyPort=8080
...
@@ -169,3 +191,5 @@ If your proxy server requires the user name and password for authentication, set
...
@@ -169,3 +191,5 @@ If your proxy server requires the user name and password for authentication, set
-[DevEco Studio Evolution Roadmap](#DevEco-Studio-Evolution-Roadmap)
-[DevEco Studio Evolution Roadmap](#section187875207166)
## About the Document
## About the Document<a name="section189422248491"></a>
DevEco Studio is an integrated development environment (IDE) of HarmonyOS apps. As HarmonyOS is developed based on OpenHarmony, DevEco Studio can also be used to develop OpenHarmony apps.
DevEco Studio is an integrated development environment \(IDE\) of HarmonyOS apps. As HarmonyOS is developed based on OpenHarmony, DevEco Studio can also be used to develop OpenHarmony apps.
The process of developing an OpenHarmony app using DevEco Studio is the same as that of developing a HarmonyOS app. This document describes the differences between OpenHarmony and HarmonyOS app development.
The process of developing an OpenHarmony app using DevEco Studio is the same as that of developing a HarmonyOS app. This document describes the differences between OpenHarmony and HarmonyOS app development.
-**Environment setup**: You need to manually install the OpenHarmony SDK for the OpenHarmony app development. For details, see [Configuring the OpenHarmony SDK](../quick-start/configuring-openharmony-sdk.md).
-**Environment setup**: You need to manually install the OpenHarmony SDK for the OpenHarmony app development. For details, see [Configuring the OpenHarmony SDK](configuring-openharmony-sdk.md).
-**Creating an OpenHarmony project**: Create a project by using the project wizard or by importing a sample project. For details, see [Using the Project Wizard to Create a Project](use-wizard-to-create-project.md).
-**Creating an OpenHarmony project**: Create a project by using the project wizard or by importing a sample project. For details, see [Using the Project Wizard to Create a Project](../quick-start/use-wizard-to-create-project.md).
-**Signature configuration for debugging**: To run an OpenHarmony app on a real device, you need to sign the app first. For instructions, see [Configuring the OpenHarmony App Signature](configuring-openharmony-app-signature.md).
-**App running on a real device**: Push the OpenHarmony HAP package to the real device for installation. For details, see [Installing and Running Your OpenHarmony App](installing-openharmony-app.md).
-**Signature configuration for debugging**: To run an OpenHarmony app on a real device, you need to sign the app first. For instructions, see [Configuring the OpenHarmony App Signature](../quick-start/configuring-openharmony-app-signature.md).
-**App running on a real device**: Push the OpenHarmony HAP package to the real device for installation. For details, see [Installing and Running Your OpenHarmony App](../quick-start/installing-openharmony-app.md).
For details about how to use DevEco Studio, see [HUAWEI DevEco Studio User Guide](https://developer.harmonyos.com/en/docs/documentation/doc-guides/tools_overview-0000001053582387).
For details about how to use DevEco Studio, see [HUAWEI DevEco Studio User Guide](https://developer.harmonyos.com/en/docs/documentation/doc-guides/tools_overview-0000001053582387).
## Restrictions<a name="section65191625782"></a>
## Restrictions
- OpenHarmony supports only app development in eTS and JS.
- OpenHarmony supports only app development in eTS and JS.
- Developing OpenHarmony apps in DevEco Studio is supported on Windows.
- Developing OpenHarmony apps in DevEco Studio is supported on Windows.
DevEco Studio serves as a development tool for both OpenHarmony and HarmonyOS apps. Refer to the following table for descriptions about the functions not supported for OpenHarmony.
DevEco Studio serves as a development tool for both OpenHarmony and HarmonyOS apps. Refer to the following table for descriptions about the functions not supported for OpenHarmony.
<trid="row15269933419"><tdclass="cellrowborder"valign="top"width="29.882988298829883%"headers="mcps1.1.4.1.1 "><pid="p152318351369"><aname="p152318351369"></a><aname="p152318351369"></a>Using DevEco Studio for log viewing and optimization</p>
<tdclass="cellrowborder"valign="top"width="36.02%"headers="mcps1.1.4.1.2 "><pid="p101251821838"><aname="p101251821838"></a><aname="p101251821838"></a>7.3 (7.2 at minimum)</p>
</td>
<tdclass="cellrowborder"valign="top"width="32.97%"headers="mcps1.1.4.1.3 "><pid="p0634643124719"><aname="p0634643124719"></a><aname="p0634643124719"></a>DevEco Studio has Gradle 7.3 preinstalled. No separate installation is required.</p>
<tdclass="cellrowborder"valign="top"width="32.97%"headers="mcps1.1.4.1.3 "><pid="p76347438478"><aname="p76347438478"></a><aname="p76347438478"></a>DevEco Studio has JDK 11 preinstalled. No separate installation is required.</p>
<tdclass="cellrowborder"valign="top"width="36.02%"headers="mcps1.1.4.1.2 "><pid="p141258211631"><aname="p141258211631"></a><aname="p141258211631"></a>3.1.0.0 (API Version 8 Beta)</p>
</td>
<tdclass="cellrowborder"valign="top"width="32.97%"headers="mcps1.1.4.1.3 "><pid="p363464312479"><aname="p363464312479"></a><aname="p363464312479"></a>This version is compatible with SDKs of earlier versions.</p>
<tdclass="cellrowborder"rowspan="3"valign="top"width="32.97%"headers="mcps1.1.4.1.3 "><pid="p14933418194918"><aname="p14933418194918"></a><aname="p14933418194918"></a>Update them to the latest version.</p>
<aname="ul1978261655712"></a><aname="ul1978261655712"></a><ulid="ul1978261655712"><li>Introduced the Chinese UI. By default, the UI is displayed in English. To enable the Chinese UI, go to <strongid="b121121320121217"><aname="b121121320121217"></a><aname="b121121320121217"></a>Settings</strong>, choose <strongid="b7112102015129"><aname="b7112102015129"></a><aname="b7112102015129"></a>Plugins</strong>><strongid="b5112152017128"><aname="b5112152017128"></a><aname="b5112152017128"></a>installed</strong>, and select <strongid="b9113182071210"><aname="b9113182071210"></a><aname="b9113182071210"></a>Chinese (Simplified)</strong>. Then, restart DevEco Studio for the settings to take effect.</li><li>Introduced support for OpenHarmony apps and services, with various debugging features, from breakpoint management and variable observation to stepping.</li></ul>
<aname="ul311913348114"></a><aname="ul311913348114"></a><ulid="ul311913348114"><li>Updated the OpenHarmony SDK to 3.1.0.0, whose API version is API 8 Beta and corresponding compilation and building plugin is 3.0.5.2.</li><li>Added an ability template that supports low-code development: <strongid="b736929122019"><aname="b736929122019"></a><aname="b736929122019"></a>[Standard]Empty Ability</strong>.</li><li>Added eTS component preview: allows previewing of eTS components; requires compileSdkVersion 8 or later.</li><li>Added eTS livee preview: allows viewing of the attribute changes in real time as you make them; requires compileSdkVersion 8 or later.</li></ul>
<tableid="simpletable19435134375015"><trid="strow1435543185020"><tdvalign="top"id="stentry64351943115013"><divclass="p"id="p13974162220455"><aname="p13974162220455"></a><aname="p13974162220455"></a><strongid="b0838112318282"><aname="b0838112318282"></a><aname="b0838112318282"></a>New Features</strong><aname="ul11381034104515"></a><aname="ul11381034104515"></a><ulid="ul11381034104515"><li>Added support for OpenHarmony SDK management. You can use SDK Manager to download and manage OpenHarmony SDKs.</li><li>Allowed for building of a single module during HAP compilation and building to accelerate building for multi-module projects; allowed for one-click re-building of HAPs, by automatically conducting the Clean Project operation before a HAP build.</li></ul>
</div>
<divclass="p"id="p556811306614"><aname="p556811306614"></a><aname="p556811306614"></a><strongid="b0183135142820"><aname="b0183135142820"></a><aname="b0183135142820"></a>Enhanced Features</strong><aname="ul834518400613"></a><aname="ul834518400613"></a><ulid="ul834518400613"><li>Updated the compilation and building plugin to version 3.0.3.2.</li><li>Improved the JSON editor, which now enables quick rectification of resource index errors and instant access to resource values.</li><li>Provided Ohos and Project (default) views for projects, which you can switch between easily.</li><li>Enabled OpenHarmony projects to support Ark build.</li><li>Moved the <strongid="b19966587296"><aname="b19966587296"></a><aname="b19966587296"></a>supportSystem "standard"</strong> field, which is exclusive to OpenHarmony projects, from the module-level <strongid="b596638162911"><aname="b596638162911"></a><aname="b596638162911"></a>build.gradle</strong> file to the project-level <strongid="b199671680295"><aname="b199671680295"></a><aname="b199671680295"></a>build.gradle</strong> file.</li></ul>
1. On the DevEco Studio welcome page, select **Configure** or click the  icon, and choose **Settings**\>**Version Control**\>**Git**. Then click **Test** to check whether the Git tool has been installed.
> This feature applies to OpenHarmony projects created using DevEco Studio 2.1 Release or later.
- If the tool has been installed, import a sample by referring to [2](#li5947194711181).
After the OpenHarmony SDK is configured, you can get started to develop your app by **importing a sample project**.
- If the tool hasn't been installed, click **Download and Install**. DevEco Studio will automatically download and install it. Then import a sample by referring to [2](#li5947194711181).
1. On the DevEco Studio welcome page, select **Configure** or click the  icon, and choose **Settings**>**Version Control**>**Git**. Then click **Test** to check whether the Git tool has been installed.
2.<aname="li5947194711181"></a>On the DevEco Studio welcome page, click **Import Sample** to import a sample project.
- If the tool has been installed, import a sample by referring to [ERROR:Invalid link:en-us_topic_0000001163914943.xml#xref1062745524418,link:#li5947194711181](#li5947194711181).
- If the tool hasn't been installed, click **Download and Install**. DevEco Studio will automatically download and install it. Then import a sample by referring to [ERROR:Invalid link:en-us_topic_0000001163914943.xml#xref2168151511810,link:#li5947194711181](#li5947194711181).
# Installing and Running Your OpenHarmony App<a name="EN-US_TOPIC_0000001115941596"></a>
You can install your OpenHarmony app in either of the following methods:
You can install your OpenHarmony app in either of the following methods:
- DevEco Studio: Connect your device where the app is stored to DevEco Studio, and then click  to install the app.
- DevEco Studio: Connect your device where the app is stored to DevEco Studio, and then click  to install the app.
- hdc: Run commands to install the app.
- hdc: Run commands to install the app.
You can manually obtain the hdc tool from the open-source repository. Then, run the tool commands to install an HAP file on the device.
You can manually obtain the hdc tool from the open-source repository. Then, run the tool commands to install an HAP file on the device.
The tool commands are as follows:
The tool commands are as follows:
- App installation
- App installation
**install [-r/-d/-g] _package_**
**install \[-r/-d/-g\] _package_**
Example:
Example:
```
```
hdc_std install E:\hwadmin.hap
hdc_std install E:\hwadmin.hap
```
```
- Log capturing
- Log capturing
**hilog**
**hilog**
Example:
Example:
...
@@ -29,4 +29,6 @@ You can install your OpenHarmony app in either of the following methods:
...
@@ -29,4 +29,6 @@ You can install your OpenHarmony app in either of the following methods:
hdc_std hilog
hdc_std hilog
```
```
For details about how to use hdc and the command format, see [hdc_std Usage Guidelines](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/oem_subsys_toolchain_hdc_guide.md).
For details about how to use hdc and the command format, see [hdc\_std Usage Guidelines](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/oem_subsys_toolchain_hdc_guide.md).
# Using the Project Wizard to Create a Project<a name="EN-US_TOPIC_0000001176969367"></a>
-[Prerequisites](#Prerequisites)
-[Prerequisites](#section13642104391619)
-[Procedure](#Procedure)
-[Procedure](#section132671712101714)
If you are using DevEco Studio 2.2 Beta1 or later, you can use the project wizard to create a project. If you are using DevEco Studio 2.1 Release, create a project by following instructions in [Importing a Sample to Create a Project](../quick-start/import-sample-to-create-project.md).
If you are using DevEco Studio 2.2 Beta1 or later, you can use the project wizard to create a project. If you are using DevEco Studio 2.1 Release, create a project by following instructions in [Importing a Sample to Create a Project](import-sample-to-create-project.md).
-**Project type**: project type, which can be an [atomic service](https://developer.harmonyos.com/en/docs/documentation/doc-guides/atomic-service-definition-0000001090840664) or an ordinary app that requires download before use.
-**Project type**: project type, which can be an [atomic service](https://developer.harmonyos.com/en/docs/documentation/doc-guides/atomic-service-definition-0000001090840664) or an ordinary app that requires download before use.
> - There is no app icon on the home screen while running or debugging an atomic service. Use the debugging and running functions of DevEco Studio as an alternative.
>- There is no app icon on the home screen while running or debugging an atomic service. Use the debugging and running functions of DevEco Studio as an alternative.
>
>- Atomic services are installation free. This is done by automatically adding the **installationFree** field to the **config.json** file, with its value set to **true**.
> - Atomic services are installation free. This is done by automatically adding the **installationFree** field to the **config.json** file, with its value set to **true**.
>- If the value of the **installationFree** field of the entry module is set to **true**, the value of the **installationFree** field of all the related HAP modules is **true** by default. If the** installationFree field** of the entry module is set to **false**, the **installationFree** field of all the related HAP modules can be set to **true** or **false**.
>
>- When compiling and building an app, make sure that the size of each HAP package does not exceed 10 MB.
> - If the value of the **installationFree** field of the entry module is set to **true**, the value of the **installationFree** field of all the related HAP modules is **true** by default. If the** installationFree field** of the entry module is set to **false**, the **installationFree** field of all the related HAP modules can be set to **true** or **false**.
>
> - When compiling and building an app, make sure that the size of each HAP package does not exceed 10 MB.
- **Bundle name**: bundle name. By default, this name will also be used as your app ID. Your app must have a unique ID to be released. If **Project type** is set to **Atomic service**, the **Bundle name** must end with **.hmservice**.
- **Bundle name**: bundle name. By default, this name will also be used as your app ID. Your app must have a unique ID to be released. If **Project type** is set to **Atomic service**, the **Bundle name** must end with **.hmservice**.
- **Save location**: local path for storing the project file.
- **Save location**: local path for storing the project file.
- **Development mode**: development mode. The **Super Visual** option is available if the project template supports low-code development.
- **Development mode**: development mode. The **Super Visual** option is available if the project template supports low-code development.
- **Language**: supported programming language.
- **Language**: supported programming language.
- **Compatible API version**: earliest SDK version compatible with your app.
- **Compatible API version**: earliest SDK version compatible with your app.
> If **compileSdkVersion 7** or later is configured for the OpenHarmony project, the corresponding module will be compiled using ArkCompiler by default. To use a compiler other than ArkCompiler, add the **arkEnable false** field to the **ohos** closure in the module-level **build.gradle** file.
>If **compileSdkVersion 7** or later is configured for the OpenHarmony project, the corresponding module will be compiled using ArkCompiler by default. To use a compiler other than ArkCompiler, add the **arkEnable false** field to the **ohos** closure in the module-level **build.gradle** file.
- **Device Type**: device type supported by the project template.
- **Device Type**: device type supported by the project template.
4. Click **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
4. Click **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
