• C++ SDK

Note the following, from the documentation for that SDK:

Caution: Firebase C++ SDK desktop support is a beta feature. This feature is intended only for workflows during the development of your game, not for publicly shipping code.

I.e., it's an SDK for testing mobile games on desktop, rather than a desktop SDK.

I guess pure Dart implementations would be the way to go then.

If we decide(e.g. I am planning to work on this) to tackle this, should we create separate issues per product and work on them accordingly?

@salihgueler I think one meta issue and discussion in the PR would work as well but It's not up to me to decide. How do you plan to implement it?

An advantage of creating multiple tickets is that we can track which firebase package is how often requested.

Is there any work being done on desktop support (other than MacOS)?

It seems like discussions cannot be used for linking to pull requests. I suggest creating individual issues for the packages and platforms.

Is there any progress here?

Any updates for windows and linux support?

The dart native option sounds like it has disadvantages:

• looks like a monumental task
• it's one more library doing the same thing as others, except in another language
• there is the c++ sdk, might as well work on that one which will also support other languages, not just dart

Can someone please give an update about the current status for Windows support. Not having windows support is causing a lot of issues for us, so need to know how long it will take for Windows support to be covered. Thanks!
cc: @Salakar

Our app has 33 dependencies. 3 do not have windows support yet. Two of them are not vital (geolocation). The only blocking dependency left that does not support windows is firebase.

almost we are in 2022 and there is no windows support. The Windows version of my app is waiting for 6 months because i built with firebase for all platforms. "firedart" extension is giving nothing to me

If firedart existed, it would allow for tree shaking of the firebase js, doesn't it ?

We as a community would like to understand why the delay, not blaming or anything. And is there anything we can help with? Like if everyone is spawning random packages to add this support, those will never be completed.

If there's a clear one repo to this support, documents, anything, clear roadmap, I believe that the community will be able to help more efficiently especially if there's also a clear leadership on this, we really want to help each other here.

Are you guys planning a big party for the 5-year anniversary?

Linux support in 2025 please

And windows please!

Throwing my voice in the din as part of the choir seeking Windows and Linux support!

Asking for Linux support. Tnx!

Another voice for Windows & Linux... Please!

This is ridiculous. Could the FlutterFire team please address this? If you guys are not going to implement this, please just say so.

Asking for Linux support

At this point I'd just settle for Messaging on windows....

Hello everyone. I notice that the team is not even looking into this issue to provide me with an answer. I wanted an app that would work across all popular platforms, but I figured I'd have to wait a few years for an answer. So I looked for an alternative and found AWS Amplify. They currently support all Flutter-compatible platforms through their Flutter plugins. With "AWS Amplify," I migrated my database from a non-relational database to a relational database, but the Flutter client code to interact with my backend hasn't changed. I'm now using a hybrid architecture. What I miss most about Firebase is its cache management. But guess what? I plan to use Firebase for mobile apps and Amplify for desktop and web to take advantage of Firebase's powerful caching system and, in the meantime, run my app on desktop and web by replicating data from Firebase to the Amplify backend via a cloud function or something similar. Amplify also has a caching system with "dataStore," but it's only available for "Amplify Gen 1" and isn't really compatible with desktop and web.

AWS Amplify has many features that Firebase doesn't and is compatible with all other services offered by AWS. It's also open source.

This made me choose Electron for my next project. It sucks, as expected, but at least I can deliver all the features my client paid me for.
At this point, it seems to me that they dropped the ball when conceptualizing the "multi-platform" aspect of the Firebase Flutter SDK, in such a way that it can't be done unless a major rewrite happens first. Which looks like it will never happen, because their focus is AI now. The framework team itself seems to have been scaled back to a minimum—hence all the recent deprecations—so it's best to move on.
I once had a dream: to work fully with a Google stack—Angular, Firebase, Flutter, and Go where Firebase couldn't reach. Can you imagine if they had managed to make all of this work seamlessly together? But instead, what we got is a dysfunctional set of frameworks with poorly managed teams that don’t seem to talk to each other.

Now, for some projects, I have to ditch this amazing piece of tech that is Flutter and work with subpar tools like React Native, all because they messed it up.

Asking for Linux support

If you can pay the service for 20ドル I can build that for you :) hahaha

function input(the_team_is_working_on_this, there_is_no_progress)
if(the_team_is_working_on_this = false && there_is_no_progress = true) {
 alert("I didn't even expect it");
} else {
 alert("wow!, it can't not be!");
}
input(false, true);

result:

clideo_editor_dbbea906ea594850b74f2ae9b383ff2b