2107 results found

1. accidentally firebase Studio workplace deleted need a recovery option

   accidentally firebase Studio workplace deleted need a recovery option

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. messaging reports you can select by year also so if you want to do a summary of 2024 example you can have access

   messaging reports you can select by year also so if you want to do a summary of 2024 example you can have access

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Field Validation

   Allow validation (e.g. min/max values, length, regex match) with custom error messages on both fields and variables. Enforce validation server-side but also provide client-side validation of variables for generated SDKs.

   41 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Data Connect  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Proposal for Local Deployment of Firebase Studio to Optimize Performance and Enable Offline Functionality
   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase ML  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Support Gemini TTS

   See https://cloud.google.com/text-to-speech/docs/gemini-tts for details. The API supports creating rich audio with accurate instruction following and allows for streaming. The benefit of adding support in AI Logic is that it greatly simplifies key management.

   Note: Live API is not a suitable replacement. Neither is an extension.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase AI Logic  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Make the AI Assistant Aware of the Current UI Mode (Preview vs. Code)

   The Problem:

   Currently, the AI assistant (Buddy) in Firebase Studio is unaware of whether the user is in "Preview Mode" or "Code Mode".

   This leads to inefficient and sometimes confusing interactions. For example, when the AI asks the user to check server logs, the user might be in Preview Mode where the terminal is not visible. This requires a back-and-forth conversation where the user has to state they can't see the logs, and the AI then has to explain how to switch to Code Mode to find the terminal.

   This entire exchange could be avoided if the AI had context about the user's current view.

   Proposed Solution:

   Please provide the current UI mode (e.g., "viewmode": "preview" or "viewmode": "code") as part of the context sent to the AI assistant with each user message.

   With this context, the AI could provide much more intelligent and direct guidance:

   If the user is in Preview Mode: "Okay, first, please switch to Code Mode using the button at the top, then check the terminal at the bottom for any new logs."
   If the user is in Code Mode: "Okay, please check the terminal at the bottom of your screen for new logs and tell me what you see."
   This small change would significantly streamline the user-AI workflow, reduce friction, and accelerate the debugging process. Thank you for considering this improvement.

   The Problem:

   Currently, the AI assistant (Buddy) in Firebase Studio is unaware of whether the user is in "Preview Mode" or "Code Mode".

   This leads to inefficient and sometimes confusing interactions. For example, when the AI asks the user to check server logs, the user might be in Preview Mode where the terminal is not visible. This requires a back-and-forth conversation where the user has to state they can't see the logs, and the AI then has to explain how to switch to Code Mode to find the terminal.

   This entire exchange could be avoided if the AI had context… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. معلومات

   احب القراءة

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  App Check  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. improve onboarding when importing repo

   When importing a repo, the placeholder text (never a good way to convey meaningful information) shows a sample url without the protocol: github.com/my-org/my-repo

   However, when trying to enter a repo url matching that example, the UI simply says "Invalid repo URL format" which is frustrating for the user because they're following the example provided

   It turns out, users need to add the protocol (https://) and then it will work. As a very early step in onboarding a repo to IDX, this can lead to frustration.

   Solution:
   1. update placeholder text to include protocol
   2. update error message to provide a potential solution, "Make sure protocol is included in URL"

   When importing a repo, the placeholder text (never a good way to convey meaningful information) shows a sample url without the protocol: github.com/my-org/my-repo

   However, when trying to enter a repo url matching that example, the UI simply says "Invalid repo URL format" which is frustrating for the user because they're following the example provided

   It turns out, users need to add the protocol (https://) and then it will work. As a very early step in onboarding a repo to IDX, this can lead to frustration.

   Solution:
   1. update placeholder text to include protocol
   2. update error message to provide a… more

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Ability to index any public docs for grounding / citations in Gemini in IDX using RAG
   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Auth onUpdate trigger for v1 and v2 functions

    In the same way, we have onCreate and onDelete, it will be very helpful to have an onUpdate option. For example, so we can react to an email address change.

    61 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Cloud Functions for Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. FI يوني

    هو تطبيق لي نشر الفيديوهات وتوجد فيه صفحتيني صفحة لي الفيديوهات وصفحة لي المنشورات ويوجد فيه روبوت ذكاء أسمه يوني وهي تتكلم مع المستخدم وتساعديه بي لغتيه وتمنع عليه الفيديوهات أو حتي المنشورات السام أو زيد ١٨ وصفحة المنشورات لا يونشري فيه الفيديوهات ولا صفحة الفيديوهات يونشر فيه المنشورات كل وحد بروحيه

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. I want to be able to clone a workspace

    I want to be able to clone a workspace, so I can have a productive environment an a separate development environment

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Suggestion: Introducing "Basic" and "Advanced" Modes in Firebase Studio for Improved UX

    I'm a regular user of Firebase Studio and truly appreciate the innovative approach of using generative AI for app development. I see huge potential here.

    However, I've noticed a gap in the user experience between the "easy app creation by talking" aspect of Firebase Studio and the "real-world development" requirements when integrating with cloud services like Firestore. Specifically, the current behavior where AI-edited firestore.rules don't reflect in the Studio's preview is causing confusion and adding friction.

    To bridge this gap and provide an optimal development experience for a wider range of users, I'd like to propose the introduction of two distinct modes in Firebase Studio:

    ---

    1. Basic Mode

    This mode would be ideal for programming beginners or those looking to rapidly prototype ideas.

    • Goal: Focus on UI/UX creation and simple interactions without deep cloud service integration.
    • Characteristics:
      • No direct integration with cloud services like Firestore or Authentication, or only with very limited dummy data for quick trials.
      • Users can concentrate on building app structure without getting into complex backend settings or security rule concepts.
    • Expected Outcome: Users can fully experience the core strength of Firebase Studio ("create apps by talking") without unnecessary friction, perfect for demos and rapid prototyping.

    ---

    2. Advanced Mode

    This mode would cater to users with some development experience who intend to build robust, production-ready applications using Firebase services like Firestore, Authentication, etc.

    • Goal: Provide a seamless and efficient workflow for serious application development.
    • Characteristics:
      • Enhanced, seamless integration with the Firestore Emulator.
        • For example: An option to switch the preview directly to an emulator connection, or a feature to instantly validate AI-edited firestore.rules using the emulator within the Studio UI.
      • Clear guidance on required knowledge: Explicitly state that certain knowledge of Authentication, data structures, security, and Cloud Functions is necessary.
      • Improved guidance on deployment processes and production environment management.
    • Expected Outcome:
      • Users can instantly and reliably validate AI-generated rule changes, enhancing trust in the AI and the overall development process.
      • A more integrated and efficient workflow for serious app development.
      • Users can choose the mode best suited to their skill level and objectives, avoiding unnecessary complexity.

    ---

    Current Challenge (Context for the Proposal)

    Currently, when the generative AI edits firestore.rules, the Firebase Studio preview doesn't reflect these changes because it connects to the live Firestore, not the local emulator. This creates confusion for users who expect to see immediate results and forces them to manually set up and use a local emulator for testing. This gap—where AI-modified content cannot be directly verified within the environment where the AI is used—is a significant UX challenge.

    I believe this proposal would significantly enhance Firebase Studio's utility and developer experience, making the AI features even more powerful and user-friendly.

    Thank you for considering this suggestion.

    I'm a regular user of Firebase Studio and truly appreciate the innovative approach of using generative AI for app development. I see huge potential here.

    However, I've noticed a gap in the user experience between the "easy app creation by talking" aspect of Firebase Studio and the "real-world development" requirements when integrating with cloud services like Firestore. Specifically, the current behavior where AI-edited firestore.rules don't reflect in the Studio's preview is causing confusion and adding friction.

    To bridge this gap and provide an optimal development experience for a wider range of users, I'd like to propose the introduction of two… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. should add a download button to get data

    how do i download files on android studio? It is disabled now.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. RSS Subscription in Firebase Studio Community
    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Simultaneously adding multiple configurations to a/b-experiment

    I would like to be able to add multiple configurations to experiment a/b at once that have been previously selected or marked. Or create an experiment based on multiple selected configurations.
    Right now, if you add configurations manually, you have to do it one at a time.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. 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, rollout,
    rotation. - Attestation gateways via App Check. - Delivery via Firebase Secrets Service. - On-device storage
    in hardware-backed keystores. - Auditability with logs and alerts.
    4) What it’s good for (and not)
    Great for: publishable keys, per-session credentials, confidential feature flags, signed URLs. Not for:
    long-term server-side secrets like DB passwords.
    5) Developer workflow
    Console/CLI creation, scope definition, rotation, logs. Example CLI: firebase secrets set
STRIPE_PUB_KEY --type=client --ttl=10m --scope app:ios:...,app:android:... --min-app-version 312
    6) SDK shape (proposed)
    Examples in Flutter, Android, iOS, Web SDKs to fetch and manage secrets securely.
    7) End-to-end flow
    1. App requests secret. 2. SDK performs attestation. 3. Secrets Service authorizes, retrieves, encrypts, returns.
    4. SDK unwraps, validates, stores. 5. Auto-refresh at half TTL.
    8) Security model & trade-offs
    Mitigates casual static extraction, stale tokens, leakage. Residual risks: rooted/jailbroken devices. Hardening:
    per-user binding, strict versioning, geo restrictions.
    9) Integrations
    Remote Config, Cloud Functions/Run, Crashlytics, Cloud Logging & Alerts.
    10) Pricing idea
    Free tier with daily limits. Paid per 10k secret fetches + GSM storage. CMEK surcharge.
    11) Example use cases
    Stripe publishable key rotation, pre-signed upload URLs, third-party SDK tokens with scope control.
    12) MVP scope
    SDKs for Android, iOS, Flutter, Web. Policies: TTL, version/platform scope, rollout, geo. Mandatory App
    Check. Console + logs.
    13) Guardrails
    Don’t put long-term secrets in clients. Expect device compromise. Never log secret values.

    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,… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Pinning or Staring the Stable State in Chat History beside Restore Button.

    Pinning or Starring the Stable File Stage in Chat History beside the Restore Button.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Firebase Studio  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Import from google drive

    Email storage

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Cloud Messaging  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating