Description of the feature request:
Add a docs/local-development.md that covers how to create a .env file after downloading, installing dependencies, running the app locally for the first time, and a step-by-step tutorial to confirm a real backend connection using a tool outside of Studio. The guide should clearly explain that Studio's preview environment is sandboxed and does not reflect live backend state, and why a terminal is required for backend-connected projects.
This PR does not cover actual deployment on Firebase or Cloud Run– it just covers how to get a local working environment as a prerequisite to to deployment.
The goal is to allow a developer who has never used Google AI Studio can download a project and run it locally without prior knowledge of Firebase or Google Cloud. The document is meant to provide a clear understanding that connections created in Google AI Studio that rely on its scaffolding are not sustained after downloading. Users will be set up to confirm backend connections as well.
What problem are you trying to solve with this feature?
There is no single document explaining how to move a Google AI Studio project into a real environment set-up. When users download their project for the first time, there is no .env file and no guidance on the fact that backend connections shown in the Studio UI may be simulated and need to be re-established after downloading. With no env file, it’s not possible to immediately connect to other Google products such as Firebase. This problem can lead to failing confirmation of connections that were confirmed in Google AI Studio’s localhost on a real environment set-up.
Any other information you'd like to share?
No response
Description of the feature request:
Add a docs/local-development.md that covers how to create a .env file after downloading, installing dependencies, running the app locally for the first time, and a step-by-step tutorial to confirm a real backend connection using a tool outside of Studio. The guide should clearly explain that Studio's preview environment is sandboxed and does not reflect live backend state, and why a terminal is required for backend-connected projects.
This PR does not cover actual deployment on Firebase or Cloud Run– it just covers how to get a local working environment as a prerequisite to to deployment.
The goal is to allow a developer who has never used Google AI Studio can download a project and run it locally without prior knowledge of Firebase or Google Cloud. The document is meant to provide a clear understanding that connections created in Google AI Studio that rely on its scaffolding are not sustained after downloading. Users will be set up to confirm backend connections as well.
What problem are you trying to solve with this feature?
There is no single document explaining how to move a Google AI Studio project into a real environment set-up. When users download their project for the first time, there is no .env file and no guidance on the fact that backend connections shown in the Studio UI may be simulated and need to be re-established after downloading. With no env file, it’s not possible to immediately connect to other Google products such as Firebase. This problem can lead to failing confirmation of connections that were confirmed in Google AI Studio’s localhost on a real environment set-up.
Any other information you'd like to share?
No response