# Package Name

The package name of an Android app uniquely identifies your app on the device, in Google Play Store and in supported third-party Android stores.

### **Step 1**

1. Open **Gradle Scripts → build.gradle (Module: app)**
2. Change the application ID with your own id name
3. Standard naming procedure : **com.yourdomainname.yourappname**
4. Click **Sync Now**.
5. Change the id as unique as possible, because application id is very important used if you want to publish the application to the google play.

{% hint style="info" %}
Important : your **applicationId or package name** must same with your package name that you’ve create on firebase console when you generate google-services.json
{% endhint %}

<div align="left"><img src="/files/-M3PyM7UYRwL4CS9Te1j" alt=""></div>

### **Step 2**

1. Click once on your package and then click setting icon on Android Studio.
2. Close / Unselect **Compact Empty Middle Packages**
3. Right click your package and rename it.

<div align="left"><img src="/files/-M3PyRquFdKPURMpT1RA" alt=""></div>

### **Step 3**

If you use OneSignal for sending push notification, you must manually change the NotificationServiceExtension value in the **AndroidManifest.xml** according to your package name

```markup
<meta-data
    android:name="com.onesignal.NotificationServiceExtension"
    android:value="<your_package_name>.notification.NotificationServiceExtension" />
```

<div align="left"><img src="/files/-Mffx0XPudcP4A6JSNMm" alt=""></div>


---

# 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://android-news-app.gitbook.io/docs/android-studio/package-name.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.