> For the complete documentation index, see [llms.txt](https://saral.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saral.sunbird.org/use/firebase-setup-for-tflite-model-deployment.md).
# Firebase setup for TFLite model deployment
Firebase setup for TFLite model deployment
### **Firstly We need an account of firebase to publish and download TFLite model**
#### **1. Enter project name:**
#### **2. Press on Continue button:**
#### **3. Select Account to continue:**
#### **4. Press on continue button:**
#### **5. Click on Android:**
#### **6. Add package name which will get from android/app/build.gradle file then once added package name click on Register button:**
#### **7. Download Service json file:**
#### **8. Do not add this dependency which is already added in project:**
#### **9. Press continue button:**
### **Firebase setup for Remote configuration to enable TFLite model**
i) If remote config flag is set as true in firebase.\
ii) Then tflite model will be downloaded in mobile once it's timer completed.\
iii) Timer can be change in RemoteConfig.java file.\
iv) Timer will be count in second.
### **There are some step for enable remote configuration which are listed below.**
#### **1. Press on Remote Config**
#### **2. Press on Create Configuration**
#### **3. Add field name with its data type and save it:**
#### **4. Click on Publish Changes**
---
# 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://saral.sunbird.org/use/firebase-setup-for-tflite-model-deployment.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.