# Main Information

## **Overview**

This is the **Basic Information Settings** screen, where required information must be entered. Developers can configure the app's **package name, service type, and ad SDK integration status** on this page.

<figure><img src="/files/9Shjarnbzf3qFVQqHbbu" alt=""><figcaption></figcaption></figure>

### **Service Classification**

Select the release status of the app.

* **Official Release**: An app officially released on ONE store.
* **Beta Release**: An app released for beta game participation purposes.

### **Package Name**

* The package name is used as a unique identifier for the app.
* **Example**: `com.example.app`
* Once registered, the package name **cannot be modified**.

### **Google Play Package Name (Optional)**

* If the same product is registered on Google Play, entering the package name improves search accuracy.
* **Example**: `com.example.app`
* Entering this information is optional, but it is recommended for **external search engine optimization (SEO)**.

### **Android Auto Compatibility**

Select whether the app supports the **Android Auto** environment for vehicles.

**If "Yes" is selected:**

* You must **agree to the Android Auto distribution terms**.
* **Verification is required**, which may take up to **7 days**.

**If "No" is selected:**

* The app will be registered as **not supporting Android Auto**.
* The related terms can be reviewed via the **\[View Terms]** button.

### **Ad SDK Integration**

**If "Yes" is selected:**

* Indicates that the app includes an **advertising SDK**.

**If "No" is selected:**

* Indicates that the app **does not use an ad SDK**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://onestore-dev.gitbook.io/dev/cht/docs/apps/android/main-info.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.