1244 results found

1. To my business and identification

   from datetime import date, datetime
   import os
   import json
   import math
   from pathlib import Path
   import ollama

   === PATHS ===

   BASEDIR = Path(file).parent.parent # Personal-AI root
   SYSTEMDIR = BASEDIR / "00-System"
   IDENTITYDIR = BASEDIR / "01-Identity-Vault"
   BUSINESSDIR = BASEDIR / "02-Business"
   KNOWLEDGEDIR = BASEDIR / "03-Knowledge"
   TASKSDIR = BASEDIR / "04-Tasks"
   LOGSDIR = BASEDIR / "05-Logs"
   RULESFILE = SYSTEMDIR / "AI-Rules.md"
   EMBEDCACHEFILE = SYSTEMDIR / "embed_cache.json"

   Embedding model

   EMBEDMODEL = "nomic-embed-text"
   CHATMODEL = "llama3.1"
   MAXFILES = 5
   CONTENTPREVIEW_CHARS = 3000

   Ensure log folder exists

   LOGSDIR.mkdir(parents=True, existok=True)

   === LOAD RULES ===

   with open(RULES_FILE, "r", encoding="utf-8") as f:
   rules = f.read()

   === EMBEDDING HELPERS ===

   def getembedding(text: str) -> list[float]:
   """Get embedding vector from Ollama. Uses the modern embed API."""
   try:
   # Prefer modern batch-capable API
   response = ollama.embed(model=EMBEDMODEL, input=text)
   return response["embeddings"][0]
   except Exception:
   # Fallback to older API if needed
   response = ollama.embeddings(model=EMBED_MODEL, prompt=text)
   return response["embedding"]

   def cosine_similarity(a: list[

   from datetime import date, datetime
   import os
   import json
   import math
   from pathlib import Path
   import ollama

   === PATHS ===

   BASEDIR = Path(file).parent.parent # Personal-AI root
   SYSTEMDIR = BASEDIR / "00-System"
   IDENTITYDIR = BASEDIR / "01-Identity-Vault"
   BUSINESSDIR = BASEDIR / "02-Business"
   KNOWLEDGEDIR = BASEDIR / "03-Knowledge"
   TASKSDIR = BASEDIR / "04-Tasks"
   LOGSDIR = BASEDIR / "05-Logs"
   RULESFILE = SYSTEMDIR / "AI-Rules.md"
   EMBEDCACHEFILE = SYSTEMDIR / "embed_cache.json"

   Embedding model

   EMBEDMODEL = "nomic-embed-text"
   CHATMODEL = "llama3.1"
   MAXFILES = 5… more

   1 vote

   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  ·  SDKs  ·  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

2. Firestore Enterprise, array indexes failure

   In Firestore Enterprise, array indexes can be created in the index management view without throwing any errors or warnings. However, when executing queries that rely on array operations (such as array-contains or array-contains-any), the query engine completely ignores the created array index and falls back to a full table scan.
   ​This creates significant issues for setups migrating from Firestore Standard, where array indexes are commonly used to handle multi-document references and array-based lookups.

   1 vote

   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  ·  Firestore  ·  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

3. Куни

   Лизание писечки

   1 vote

   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  ·  Agent Skills & MCP Server  ·  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

4. Unable to update Action URL / Subject for email templates — EMAIL_TEMPLATE_UPDATE_NOT_ALLOWED

   Subject: Unable to update Action URL / Subject for email templates — EMAILTEMPLATEUPDATENOTALLOWED

   Project ID: charitey-37ce8
   Project name: Fourth Idly

   Description:

   I'm trying to customize the password reset email template for my Firebase Authentication project. Specifically, I need to update:

   The Action URL (currently https://charitey-37ce8.web.app/__/auth/action) to point to my custom domain
   The email subject line

   Both attempts fail with the same result:

   Via Firebase Console: Clicking "Save" on Authentication → Templates → Password reset → Customize action URL shows a generic error: "An error occurred updating action URL."
   Via the Identity Toolkit REST API (projects.updateConfig with updateMask=notification.sendEmail.callbackUri), the request returns:
   {
   "error": {
   "code": 400,
   "message": "EMAILTEMPLATEUPDATENOTALLOWED",
   "status": "INVALID_ARGUMENT"
   }
   }

   Other fields (sender name, from-address, reply-to) update successfully through the same console page — only the Action URL and Subject are refused.

   Could you please look into why this project has this restriction, and lift it if possible? This is blocking normal branding customization for a production app.

   Thank you

   Subject: Unable to update Action URL / Subject for email templates — EMAILTEMPLATEUPDATENOTALLOWED

   Project ID: charitey-37ce8
   Project name: Fourth Idly

   Description:

   I'm trying to customize the password reset email template for my Firebase Authentication project. Specifically, I need to update:

   The Action URL (currently https://charitey-37ce8.web.app/__/auth/action) to point to my custom domain
   The email subject line

   Both attempts fail with the same result:

   Via Firebase Console: Clicking "Save" on Authentication → Templates → Password reset → Customize action URL shows a generic error: "An error occurred updating action URL."
   Via the Identity Toolkit REST API (projects.updateConfig… more

   2 votes

   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

   2 comments  ·  Authentication  ·  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. Shadrack

   import 'package:flutter/material.dart';
   import 'package:firebasecore/firebasecore.dart';

   // Import the firebaseappcheck plugin
   import 'package:firebaseappcheck/firebaseappcheck.dart';

   Future<void> main() async {
   WidgetsFlutterBinding.ensureInitialized();
   await Firebase.initializeApp();
   await FirebaseAppCheck.instance.activate(
   // You can also use a ReCaptchaEnterpriseProvider provider instance as an
   // argument for webProvider
   webProvider: ReCaptchaV3Provider('recaptcha-v3-site-key'),
   // Default provider for Android is the Play Integrity provider. You can use the "AndroidProvider" enum to choose
   // your preferred provider. Choose from:
   // 1. Debug provider
   // 2. Safety Net provider
   // 3. Play Integrity provider
   androidProvider: AndroidProvider.debug,
   // Default provider for iOS/macOS is the Device Check provider. You can use the "AppleProvider" enum to choose
   // your preferred provider. Choose from:
   // 1. Debug provider
   // 2. Device Check provider
   // 3. App Attest provider
   // 4. App Attest provider with fallback to Device Check provider (App Attest provider is only available on iOS 14.0+, macOS 14.0+)
   appleProvider: AppleProvider.appAttest,
   );
   runApp(App());
   }

   import 'package:flutter/material.dart';
   import 'package:firebasecore/firebasecore.dart';

   // Import the firebaseappcheck plugin
   import 'package:firebaseappcheck/firebaseappcheck.dart';

   Future<void> main() async {
   WidgetsFlutterBinding.ensureInitialized();
   await Firebase.initializeApp();
   await FirebaseAppCheck.instance.activate(
   // You can also use a ReCaptchaEnterpriseProvider provider instance as an
   // argument for webProvider
   webProvider: ReCaptchaV3Provider('recaptcha-v3-site-key'),
   // Default provider for Android is the Play Integrity provider. You can use the "AndroidProvider" enum to choose
   // your preferred provider. Choose from:
   // 1. Debug provider
   // 2. Safety Net provider
   // 3. Play Integrity provider
   androidProvider: AndroidProvider.debug,
   // Default provider for iOS/macOS is the Device Check provider. You can use the "AppleProvider"… more

   1 vote

   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 Distribution  ·  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. Provide an Nx plugin or support the community one

   There's a plugin, but it doesn't receive much love. The main problem is effort - Nx keeps doing breaking changes and the plugin gets broken with pretty much every new Nx version. Not even to mention that they dropped the e2e part for functions.

   Would be great if the Firebase Team could work on it:

   https://github.com/simondotm/nx-firebase

   1 vote

   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

7. Fr Tournaments

   Nuralom

   1 vote

   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  ·  Cloud Functions for Firebase  ·  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. Feature Request: Support for Zstandard (zstd) Compression

   💡 Feature Proposal

   Is your feature request related to a problem? Please describe.
   Currently, Firebase Crashlytics (both the backend and the upload-symbols / Gradle tooling) strictly requires standard .zip (DEFLATE) archives for symbolication files like dSYMs and ProGuard mappings.

   For large-scale applications, dSYM files can easily grow to several gigabytes. Compressing them with standard single-threaded zip tools slows down CI/CD pipelines significantly, while multi-threaded tools or better algorithms cannot be fully utilized because the Firebase backend rejects anything other than standard ZIP files.

   Describe the solution you'd like
   We would like Firebase Crashlytics to natively support Zstandard (.zst or .tar.zst) compression for symbol files uploads (via Web Console, Fastlane, and CLI/Gradle plugins).

   Zstd provides a dramatically better compression/decompression speeds and ratios compared to DEFLATE (Gzip/Zip). Integrating it into the upload-symbols binary and Crashlytics backend would allow:
   1. Faster archiving stages on CI runners (saving expensive compute minutes).
   2. Smaller payload sizes, reducing network transit times when pushing symbols to Firebase.

   Describe alternatives you've considered
   - Using multi-threaded ZIP alternatives like pigz -K, which helps with CPU times but doesn't solve the compression ratio limits of the older DEFLATE algorithm.
   - Uncompressing .zst archives on intermediate CI stages just to feed raw directories into upload-symbols, which wastes disk I/O and runner storage.

   Additional context
   Many modern engineering pipelines and data lakes have already migrated to Zstd as their default compression standard. Bringing native Zstd support to Crashlytics symbol uploads would highly optimize modern mobile CI/CD workflows (especially for heavy enterprise iOS/Android apps).

   💡 Feature Proposal

   Is your feature request related to a problem? Please describe.
   Currently, Firebase Crashlytics (both the backend and the upload-symbols / Gradle tooling) strictly requires standard .zip (DEFLATE) archives for symbolication files like dSYMs and ProGuard mappings.

   For large-scale applications, dSYM files can easily grow to several gigabytes. Compressing them with standard single-threaded zip tools slows down CI/CD pipelines significantly, while multi-threaded tools or better algorithms cannot be fully utilized because the Firebase backend rejects anything other than standard ZIP files.

   Describe the solution you'd like
   We would like Firebase Crashlytics to natively support Zstandard (.zst or … more

   1 vote

   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  ·  Crashlytics  ·  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

9. Feature Request: Include Crashlytics issue notes in BigQuery Export

   Hi Firebase Team,

   I would like to submit a feature request regarding Firebase Crashlytics and BigQuery Export.

   Currently, our team uses the notes section in Crashlytics to manage crash investigation statuses and review progress. While Crashlytics provides great BigQuery integration for raw event data, the issue notes are not included in the exported dataset.

   To improve our operational workflow, we would love to see issue notes included in the BigQuery Export schema. Even if it only exports the latest note associated with each issue, it would allow us to write custom SQL queries and build live dashboards (e.g., in Looker Studio) to track resolution progress across our organization.

   Having this capability would greatly enhance our reporting and data analysis efficiency.

   Thank you for considering this request!

   Best regards,

   Hi Firebase Team,

   I would like to submit a feature request regarding Firebase Crashlytics and BigQuery Export.

   Currently, our team uses the notes section in Crashlytics to manage crash investigation statuses and review progress. While Crashlytics provides great BigQuery integration for raw event data, the issue notes are not included in the exported dataset.

   To improve our operational workflow, we would love to see issue notes included in the BigQuery Export schema. Even if it only exports the latest note associated with each issue, it would allow us to write custom SQL queries and build live dashboards (e.g., in Looker… more

   1 vote

   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  ·  Crashlytics  ·  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

10. Keep Firebase Studio alive until Google offers a real replacement

    Firebase Studio is being shut down without a true replacement, and that is a serious mistake.

    For many of us, Firebase Studio was not just an experiment — it was a practical, browser-based development workspace deeply integrated with Firebase, accessible from anywhere, and useful for real production workflows.

    The alternatives being pointed to are not equivalent:

    Google AI Studio is more of an AI playground than a full development environment.
    Antigravity appears to require high-end local hardware, which defeats the purpose of a cloud-based workspace you can use from any machine.
    Firebase Studio gave developers something extremely valuable: flexibility, accessibility, low hardware dependency, and direct connection to Firebase projects. Removing it without feature parity is not a migration — it’s a downgrade.

    We ask Google to:

    delay the shutdown of Firebase Studio until there is a true replacement;
    publish a clear roadmap for feature parity;
    clarify what will happen to users who paid for extra workspaces;
    listen to the community before removing a tool that many developers genuinely rely on.
    If Firebase Studio has been part of your workflow, please sign and help show Google that this product should not disappear without a proper alternative.

    Firebase Studio is being shut down without a true replacement, and that is a serious mistake.

    For many of us, Firebase Studio was not just an experiment — it was a practical, browser-based development workspace deeply integrated with Firebase, accessible from anywhere, and useful for real production workflows.

    The alternatives being pointed to are not equivalent:

    Google AI Studio is more of an AI playground than a full development environment.
    Antigravity appears to require high-end local hardware, which defeats the purpose of a cloud-based workspace you can use from any machine.
    Firebase Studio gave developers something extremely valuable: flexibility, accessibility,… more

    1 vote

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

11. Shamefull

    Its literally very much shameful how google operates. I tried multiple times to buy google cloud, google studio, and firebase but each time what i see is they deduct 2 Rs and set autopay but decline that you were not able to set your payment method. I tried this so many times but got the same results. if you guyz don't accept upi then why you give option to select. its really very upsetting. how can i trust you guyz when you take 2 Rs multiple times and doesn't validate the autopay then how can i be assured that you will not cut 15k as you set up the autopay for 15k and if i try that 10-20 times to setup autopay then ........ its really out of the mind kind of thoughts that coming in my mind. because who can expect google doing golmaal. such a shame

    Its literally very much shameful how google operates. I tried multiple times to buy google cloud, google studio, and firebase but each time what i see is they deduct 2 Rs and set autopay but decline that you were not able to set your payment method. I tried this so many times but got the same results. if you guyz don't accept upi then why you give option to select. its really very upsetting. how can i trust you guyz when you take 2 Rs multiple times and doesn't validate the autopay then how can i be assured that you… more

    1 vote

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

12. Firestore Console: Option to keep original sub-field order when sorting documents

    It would be great to have a feature where sorting/filters applied at the collection level do not automatically apply to nested sub-fields, or an option to disable parent sorting on individual fields in the console viewer.

    While this doesn't change the underlying dataset, it would make manual data inspection much more convenient and intuitive for human reviewers.

    1 vote

    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  ·  Firestore  ·  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. Talk need to talk with them using audio or video.", live streem audio and video sharing

    Anything

    1 vote

    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  ·  In-App Messaging  ·  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

14. WEIRD LOOKING LONG VERIFICATION LINKS

    This concerns the verification links. Since we cannot edit the HTML body directly, the long default Firebase links can look intimidating to users, making them hesitant to click. Would it be possible for Firebase to format these links as buttons by default across the platform? I believe this improvement would be highly beneficial for many developers and users.

    1 vote

    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  ·  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

15. Please remove all the AI stuff about having Gemini write us a barista app

    The Firebase console used to be intuitive to navigate. Now if I am trying to find my Crashlytics settings there are all these buttons in my face inviting me to let Gemini create a barista app. No one wants to create a barista app, can you please move all this stuff over to some other system hyping agents somewhere else?

    1 vote

    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 console  ·  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

16. Back up it

    Interested

    2 votes

    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  ·  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. Our Project has been suspended last two days

    Our Project is suspended from last two days and has been restored yet..

    2 votes

    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 console  ·  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. Anyone can exhaust your Auth quota and take the project down

    Rejected requests to identitytoolkit (401 invalid App Check, 400 per-IP) and securetoken (refresh) still count against the project quotas (1,000 QPS, 10M/day, 18,000/min) — confirmed by measurement and Firebase Support (case #10417533). A single IP with no valid credentials can consume shared quota. Developers have no WAF or per-IP rate limiting for these client-facing endpoints, and no supported mitigation, so an external party can force an Auth availability outage on any project using client-side Auth.

    AWS Cognito solves this: attach a WAF web ACL to a user pool, and blocked requests don't count toward quota. Please add equivalent edge filtering for Firebase Auth.

    Rejected requests to identitytoolkit (401 invalid App Check, 400 per-IP) and securetoken (refresh) still count against the project quotas (1,000 QPS, 10M/day, 18,000/min) — confirmed by measurement and Firebase Support (case #10417533). A single IP with no valid credentials can consume shared quota. Developers have no WAF or per-IP rate limiting for these client-facing endpoints, and no supported mitigation, so an external party can force an Auth availability outage on any project using client-side Auth.

    AWS Cognito solves this: attach a WAF web ACL to a user pool, and blocked requests don't count toward quota. Please add equivalent edge filtering… more

    6 votes

    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  ·  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. I dislike your new UI for A/B testing; it's extremely difficult to use. Configurations aren't readily apparent; the page shrinks to the righ

    I dislike your new UI for A/B testing; it's extremely difficult to use. Configurations aren't readily apparent; the page shrinks to the right sidebar, which is visually unpleasant. New configurations can't be created immediately, unlike in the previous mode. Starting a test requires creating a new condition; otherwise, the test won't be at the highest priority under the same configuration, and users will end up using other conditions within the same configuration. It's difficult to use, very difficult to use.

    2 votes

    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  ·  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

20. First-class Firebase SDK support for Kotlin/Wasm and Compose Multiplatform Web

    Please add first-class Firebase SDK support for Kotlin/Wasm, especially for Compose Multiplatform Web apps.

    Kotlin/Wasm is becoming an important target for sharing Kotlin and Compose UI across Android and Web. Today, Firebase works well on Android and through the JavaScript SDK on Web, but Kotlin/Wasm integration is still awkward and requires wrappers, JS interop, REST calls, or platform-specific abstractions.

    It would be very useful to have official support for Auth, Remote Config, Realtime Database, Firestore, Analytics, and Storage from Kotlin/Wasm.

    2 votes

    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  ·  SDKs  ·  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