Hello Firebase Studio Team,
I am using Firebase Studio for Flutter development and I am facing multiple issues that significantly impact productivity. I would like to report them together for better clarity.
1. Android Emulator instability
The Android Emulator in Firebase Studio does not work reliably.
In many cases it fails to start properly or becomes unresponsive, making mobile testing difficult.
2. pubspec.yaml project name and Explorer label mismatch
In the pubspec.yaml file, the default project name is set to “myapp”.
At the same time, Firebase Studio highlights the project in the Explorer as “MYAPP”
instead of the actual project/repository name (e.g., Billing-Hub).
This behavior is confusing, especially for beginners, as users expect the project
name shown in the Explorer to reflect the real app or folder name by default.
3. APK build not supported
There is no clear or supported way to generate an APK from Firebase Studio.
This limits the ability to test or share builds outside the emulator.
4. No Chrome or Edge device for Flutter Web
Only the following devices are available:
-
Web Server
-
Linux
-
Android Emulator
Chrome or Edge are not available as run targets, yet the logs suggest:
“Consider using the Chrome or Edge devices for an improved development workflow.”
Since Firebase Studio runs in a cloud environment, Chrome/Edge cannot be selected, which makes this message confusing.
Overall, these issues make Flutter Web and Android development harder inside Firebase Studio.
It would be very helpful to have:
**- More stable emulator support
-
Clearer project naming defaults
-
APK build support or documentation
-
Firebase-Studio-specific guidance for Flutter Web debugging**
Environment:
-
Firebase Studio (cloud)
-
Flutter (Web & Android)
-
OS: Cloud-based environment
Thank you for your work and I hope this feedback helps improve Firebase Studio.
Best regards,
Sweety