> For the complete documentation index, see [llms.txt](https://md-s-organization-1.gitbook.io/fly_tv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://md-s-organization-1.gitbook.io/fly_tv/project-customization/change-applicationid.md).

# Change ApplicationId

To change the <mark style="color:orange;">**applicationId**</mark>, navigate to the <mark style="color:orange;">**build.gradle.kts**</mark> file at the <mark style="color:orange;">app level</mark>. In the <mark style="color:orange;">productFlavors</mark> block, modify the <mark style="color:orange;">applicationId</mark> in the pro block to your desired ID for the production release. Additionally, you can change the <mark style="color:orange;">applicationId</mark> in the dev block for testing purposes during development. Ensure that you use distinct applicationIds for <mark style="color:orange;">**dev**</mark> and <mark style="color:orange;">**pro**</mark> modes. For example, you can use "<mark style="color:orange;">com.example.anything.dev</mark>" for the <mark style="color:orange;">dev</mark> mode and "<mark style="color:orange;">com.example.anything</mark>" for the <mark style="color:orange;">pro</mark> mode.

<mark style="color:red;">Indeed, changing the applicationId can potentially cause errors, especially in the context of Firebase configuration. However, there's no need to worry about it at this stage. We'll proceed to configure Firebase, and everything should work seamlessly afterward.</mark>

<figure><img src="https://2247592170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FZzlNz37Z2cHlcbKgcr%2Fuploads%2FjbOoWkybPd682nC5g8cT%2FScreenshot%202024-03-28%20at%207.04.41%E2%80%AFPM.png?alt=media&amp;token=f8dd8a0a-f917-4df0-9e7d-7360e966221e" alt=""><figcaption><p>if you change the dev applicaitonId also .then configure the firebase also for the dev flavour .as same as pro flavour . </p></figcaption></figure>