2133 results found
-
Install extensions on certain project/environment only
I'd like to have an option to install an extension for certain project in my code base.
For example, I want to use algolia search extension on a collection that will only only exists in dev project, but I ended up deploying this extension in prod as well.
I can't seem to find a way not to deploy extensions that are meant to be in dev only to prod.
1 vote -
waiting for get access to Project IDX to explore the features
I am in waiting list, please give the access to use
1 vote -
Firestore Blocking Functions
Blocking functions for Firestore e.g. block writing a document until a certain condition is met
7 votes -
Firebase In-App Messaging
Currenty I do not see any option to "Compose a campaign" via APIs. If we could open up all the inapp creation/management interactions via APIs, it would be easy for companies to leverage those to customize their composing experience.
3 votes -
Support for Jetpack Compose in Analytics and PerfMon
Right now, there is no support for Jetpack Compose. If you have a single Activity and use composables to navigate through your app, without custom events, nothing is really tracked. So the request add navigate support for screen views based on composables like we have for Activities and Fragments.
11 votes -
Allow Android/iOS apps to select dynamically which Firebase project should be used on startup
Some scenarios require dynamically switching from one Firebase project to another, including Analytics and Crashlytics, For example, switching from a Firebase project set up for a staging environment (which requires to collect Analytics and crashes) to another set up for a production environment.
There could be many solutions to this problem, such as having multiple plist/json files and switching them dynamically, or no longer requiring these files and simply using object instances that store the configuration (e.g., using the FirebaseOptions builder). The best solution should satisfy the scenario described above.
This idea comes from this issue https://github.com/firebase/firebase-android-sdk/issues/66
11 votes -
12 votes
-
List of all error codes in auth (Not the admin SDK)
Currently there is only a list of error codes the Admin SDK can receive, not for the web sdk.
5 votes -
Tailwind Css IntelliSense Support / Extension
Currently, the IDX lacks Tailwind CSS IntelliSense support or extension, and I believe incorporating this feature would be immensely beneficial for developers like me who heavily rely on Tailwind CSS for efficient and streamlined styling. Tailwind CSS IntelliSense would not only improve coding speed but also reduce errors and enhance overall productivity.
1 vote -
Hubspot - hubl + html language support
It would be great if idx support hubl + html.
1 vote -
Make mapped URLs to work seamlessly between projects
If I have different services across different projects (E. g. an Angular font end and an NestJS back end) there should be a way to set the jwt cookie automatically for the front end to communicate with the backend in the preview despite the back end and front end being in different IDX projects
2 votes -
Make it easier to see Next.js dev server output.
It took me a long time to find the dev server output (in Output under IDX). It would be nice if it was easier to find.
6 votes -
Hosting CDN cache stale-while-revalidate
Time-to-first-byte from Firebase Functions is usually slow (more than 500ms) even without cold start, sometimes (with cold starts) TTFB becomes absolutely unacceptable for projects where performance is important. SSRed HTML is also not Brotli compressed as static files.
This is a really big problem to deploy SSR web apps to Firebase IMO, and cache SWR at the CDN layer (edge) would solve it perfectly.5 votes -
Crashlytics will report different stacks as different crash
Currently exception events are gathered as one issue depending solely on the actual exception location and its type.
Moreover, every such event pops all previous ones as regressed.
This makes it hard to follow the different issues. It is specifically a big problem where a fallback is used, with non-fatal crash reports in it. All crashes that ended up with the fallback are reported as one.
My suggestion is that different call stack and/or message will be shown as different issues. (Possibly with an option to set the differing place in the stack)2 votes -
Set GCP resource location locally or have it be faked when using Firebase without a project.
I'm currently learning Firebase and want to have a sandbox with the emulators without creating a project on the website every time I want to make another. Currently Firebase Storage does not work without setting a GCP resource location and the only way to set it is via the web console. If there was a way to set it locally via the CLI or a config file that would make it a lot easier to experiment with Firebase.
2 votes -
Authenticate via email code
We can now use passwordless authentication using email link. This is troublesome on Flutter web clients (a new tab/second instance of app is opened). An option to type 4 digit code received on email to authenticate would be a nice solution.
BTW. Let me know if you could help me with the email link web client authentication, thanks!6 votes -
TTL for Realtime DB
Realtime DB is very similar to Redis functionality. It would be very valuable to enable real caching behaviour by adding time to live to an entry.
12 votes -
Support "Continuing Uploads Across Process Restarts" on iOS
I work for a company that enable people to record sports using video and the storage footprint are often very huge (10GB+). While building an app for iOS, I notice that Firebase don't support continuing uploads across process restarts on iOS which is a major deal-breaker for continuing using Cloud Storage for Firebase.
I see support for this on Android and I will encourage you to add this to iOS in the future. Ref: https://firebase.google.com/docs/storage/android/upload-files#continuing_uploads_across_process_restarts5 votes -
Green/Blue deployment pattern
Allow for deployments to be either a green or blue deployment to be able to have multiple instances of the same functions deployed within a single Firebase project.
This would help cover the gap of time between releases of client apps and Cloud Functions, which if not handled correctly cause production issues.
3 votes -
Firebase AppCheck (something like ReCaptcha Enterprise) for Expo React Native Android web app projects
How can I install Firebase AppCheck in my Expo React Native Android web app project? This app is deployed on Google play console registered as webapp on firebase.
ReCaptcha Enterprise
1 vote
- Don't see your idea?