2141 results found
-
Allow changing the form of email links to a deep link
Currently, Apple app links can require up to 24 hours to start working (due to a delay on downloading the AASA files). This can be worked around by using a deep link instead in the form of myapp://mydomain. When links are generated server-side, I can change the form myself, but that isn't possible client-side.
1 vote -
App Secrets
Firebase App Secrets ̶ Runtime Secrets for Mobile & Web
1) Problem
Developers routinely ship API keys and tokens in apps. Obfuscation isn’t protection; true secrets must be
short-lived, scoped, and revocable. Today, Firebase offers Cloud Secret Manager (great for servers) and App
Check/Play Integrity (great for attestation), but there’s no first-class, managed way to deliver ephemeral,
policy-controlled secrets to client apps.
2) One-liner
“Deliver short-lived, policy-scoped secrets to verified client apps with automatic rotation, attestation, and
device-secure storage̶built into Firebase.”
3) Core concepts
- Vault: Secrets stored in Google Cloud Secret Manager with optional CMEK. - Policies: TTL, scope,…1 vote -
1 vote
-
التواصل
التواصل بين الشعوب
1 vote -
the prototyper should be able to take files like json , html , javascript , pdf and other files
the prototyper should be able to take files like json , html , javascript , pdf and other files
2 votes -
Jazz cash payment meathod
All meathod payment pay Jazz cash and number pay
1 vote -
1 vote
-
App greenlight community to connect developers with potential investors
Public or private community page for displaying completed apps in order to connect developers with potential investors or monetization opportunities. Alternatively, each developer could have a public facing page to display their projects like a social media page. Could implement voting system, feedback, monetization for donations, and a light social aspect for potential collaboration, career, or investment opportunities.
1 vote -
Live preview of a change before making it.
If developing a small part of the app, like a table, or container with buttons, the prototyper could show a live preview of that feature to more quickly optimize the design before updating the whole code. This would be limited to features that don't integrate with the rest of the prototyped app, or would have dumb buttons instead of actionable buttons.
3 votes -
1 vote
-
Helpful Meta Action Buttons
It would be great if there was a quick way to trigger certain insightful checks or reports of a user's project that show in a popup, for example:
--Architectural diagram of what this project looks like
--ERD/schema diagram
--Performance report with ideas for improvements
--Lighthouse test with clickable actions to address
--GCP calculator report for monthly usage
--Check for any unused code with clickable removal1 vote -
Clear Gemini History Not Working
Sorry, I hit a snag. Please try again shortly or modify your prompt.
[GoogleGenerativeAI Error]: Error fetching from https://monospace-pa.googleapis.com/v1/models/gemini-2.5-pro:streamGenerateContent?alt=sse: [400 Bad Request] The input token count (9521395) exceeds the maximum number of tokens allowed (1048576).When you try to clear the history on Gemini, this doesn't work. This needs to be fixed, otherwise it prevents vibe coding, etc.
3 votes -
Confirmation Before Firebase AI Applies Changes
With the rise of AI-assisted development, many of us are used to casually chatting with AI — sometimes just asking for suggestions or even giving compliments. However, in Firebase, I’ve noticed that AI often directly applies comments/requests to the project without asking for confirmation.
This can be frustrating and risky, since a casual message can unintentionally trigger real changes to the project.
Suggestion:
Add a confirmation dialog (or toggle in settings) that controls whether Firebase AI should:
Directly implement all requests automatically, or
Confirm with the developer first before making any changes.
Benefits:
Prevents accidental or unintended project changes.
Lets…
6 votes -
Built-in App Versioning & Rollback Feature
I’ve faced repeated issues in Firebase where making updates or major changes can lead to fatal errors. The biggest frustration is that even the rollback request often fails, leaving no reliable way to restore the project to a stable state.
Because of this, the only solution I’m forced to use is creating a full duplicate of the entire project every time I want to make major changes. This is inefficient, time-consuming, and increases the risk of inconsistencies.
- * * Suggestion:
Introduce built-in versioning for apps (e.g., 1.0.0.01, following semantic versioning best practices).
Each update/deployment should automatically create a new version…
3 votes -
Firebase studio project restoration from trash if deleted
There should be a trash box
2 votes -
Merging projects
It would be nice to be able to merge projects. If you have multiple apps that may need to communicated to one another and read from the same data base, but you dont want to build a monolith, you should be able to merge the projects in a way that you can build the functionality between the apps so they can all talk to one another
4 votes -
One-Click Edit and Remove Feature for Generated Code
I think Firebase should provide an option that allows users to easily edit their previous messages and remove any previously generated code with a single click. This would improve the user experience by making code management and corrections faster and more convenient.
1 vote -
Debian, Ubuntu, more machine types, and root privileges
Debian/Ubuntu is because for a familiar environment as not everyone knows Nix. [Nix should be optional option to select OS, not enforced. Nix does not follow the FHS.]
More machine types for prototyping apps (and their dependencies) that require high specifications. [because there are apps that are resource intensive to compile.]
Root privileges for control over the environment. [because if someone wants to install X that is not available on any of Nix, they might need root access to install it on the root folder (/).]3 votes -
Debian, Ubuntu, more machine types, and root privileges
Debian/Ubuntu is because for a familiar environment as not everyone knows Nix. [Nix should be optional option to select OS, not enforced. Nix does not follow the FHS.]
More machine types for prototyping apps (and their dependencies) that require high specifications. [because there are apps that are resource intensive to compile.]
Root privileges for control over the environment. [because if someone wants to install X that is not available on any of Nix, they might need root access to install it on the root folder (/).]1 vote -
A M-pesa app but cheaper on transactions
Cheapest app on transactions
2 votes
- Don't see your idea?