> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/masterstudy-app-documentation/android-app-build-on-macos/change-package-name.md).
# Change Package Name
All Android apps have a package name. The package name uniquely identifies the app on the device; it is also unique in the Google Play store.
In MasterStudy App there is a specific package name that is used: **com.example.masterstudy\_app.** You should change it to your own package name, for example, **com.mycompany.name** where the Mycomapny will be the name of your brand.
To change the package name you need to follow some steps.
First you need open **android** folder in AndroidStudio
In your **Project panel**, click on the little gear icon.
Uncheck the option Compact Empty Middle Packages
Your package directory will be broken into individual directories
Individually select the directory you want to rename, and follow these steps:
Right-click it >> Select **Refactor** >> Click on **Rename**
Enter the new name and hit **Refactor**
Click **Do Refactor** in the bottom and wait a minute to let Android Studio update all changes.
> Note: When renaming com in Android Studio, it might give a warning. In such case, select Rename All.
Edit **build.gradle (Module: app)** file in the **Gradle Scripts**
Find the **50th line** and change “com.stylemixthemes.masterstudyapp” to your package name.
After that click on **Sync Now** to synchronize Gradle.
Then go to **App > Manifests** and edit the file AndroidManifest.xml if it wasn't changed automatically.
From the Android Studio menu open **Build** and click on the **Clean Project**. Wait until Android Studio finishes the process.
After that, in the same menu find and launch **Rebuild Project**.
This is the final step in changing the package name.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.stylemixthemes.com/masterstudy-app-documentation/android-app-build-on-macos/change-package-name.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
