2085 results found
-
Add different release tracks
Right now Firebase app distribution only allows a big flat list of APKs. We want to have a functionality where we can create different tracks such as daily builds, pre release builds, develop builds etc. to help us better manage the different builds and also our users to better select which build they want to install and test
1 vote -
Obfuscate or hide GoogleService-Info.plist
Secret information in GoogleService-Info.plist is easily accessible by downloading .ipa from App Store via Apple Configurator and unpacking it. That is a big security issue.
1 vote -
Add kill switch in the console
There really should be a big red switch in the Firebase console to temporarily disable the application.
If I'm under DOS attack or critical security/privacy issue got exposed I need a very quick way to shutdown the service temporarily until the fix is ready.
You will not need it until you need it!It seems only possible from CLI, and having the right version of CLI handy in the not so active project is close to impossible, so this is really a console requirement.
1 vote -
Localize
I would like the ability to be able to localize notifications like we can with in-app messages please. Because as it is now, we have to make a separate message for each language which uses up our allotted messages limit quickly.
1 vote -
Control Over Frequency
I would like control over the frequency of the in-app messages popping up in 1 session. If a user is eligible for 3 messages I dont want them popping up one after another. I would like the ability to space them out by minutes, hours, days or sessions please. And what about being able to make a slideshow of images as an in-app message?
1 vote -
1 vote
-
1 vote
-
یک نرم افزار قرعه کشی
نرم افزار کم حجم باشد
1 vote -
I will design a
Designer
1 vote -
1 vote
-
1 vote
-
Local File Intelligence Pipeline using Firebase Emulators and Gemini.
This system runs entirely on your local machine using the Firebase Emulator Suite, which simulates the Firebase cloud environment. It connects a local file system event to the Gemini API for analysis.
Core Components:
Local File Watcher: A simple script (e.g., using Node.js with the chokidar library) that monitors specific folders on your computer for new files.
Firebase Emulator Suite: Your local "cloud" containing:
Cloud Storage Emulator: To temporarily hold the file being processed.
Cloud Functions Emulator: To run the AI logic when a new file is added.
Firestore Emulator: To store the structured AI results.
Google AI (Gemini API):…
0 votes -
Avoiding mock functions, placeholders, and demo functions.
A recurring problem with Gemini is that when asked to implement functions, it often generates mock functions, placeholders, or demo code instead of real, production-ready logic. This makes the output more suitable for prototypes and proofs of concept, but useless in actual development or production environments. To solve this, Gemini should follow a strict mode-based rule. In prototype mode, it may generate mock data or placeholder functions for quick demonstrations. However, in development or production mode, it must always deliver fully functional, non-mock implementations. This ensures projects remain practical, reliable, and ready for real-world deployment.
1 vote -
Avoiding mock functions, placeholders, and demo functions.
Gemini should be told a rule that never provide mock functions, placeholders and demo
most of the time i see this issue, when i asked it to add a function it add mock functions, just a demo project.
this is making useless projects it mean only that firebase studio can be only used for prototype.
In rules, which it should always follow this rule can be set as mode
if mode is prototype then it can go for placeholders and mock data but if its development or production then this is useless with mock or placeholder building the apps.I…
1 vote -
1 vote
-
only 5 projects should be able to have 30 projects?
needing to add more projects
2 votes -
Origen360
ArroyoIA.com
1 vote -
1 vote
-
Map Firebase Data Connect (FDC) schema to custom postgres schema (not PUBLIC)
Currently, any gql files placed in schema folder generate one FDC schema in FDC console, which generates associated tables in postgres PUBLIC schema. Putting tables there is not ideal.
It would be nice if creating additional subfolders within schema source folder (or some other mechanism) could allow mapping to developer defined postgres schemas other than PUBLIC. For example, the following folder structure:
schema/appname/*.gql
would map to APPNAME schema in Postgres and tables would be created there.
1 vote -
1 vote
- Don't see your idea?