dio VS flutterfire

With no release in the last 6 months, piling up of issues and launch of a new fork (diox), I felt something was going on with dio. Sadly, today I came across an official announcement (updated on the project repo 2 days back):

You might want to think twice about dio....we evaluated dio on a recent project and decided to avoid it after running into a blocker when setting a custom timeout (this bug: https://github.com/flutterchina/dio/issues/1454)

- and Dio for http requests

I also had some troubles choosing which Dart HTTP client to use. I've started with dio, but when I tried to read one of our bigger JSON responses (~1.5mb) my browser tab froze (there seems to be an old issue describing the same behavior). After that I've switched to the default dart's http package and it is working fine but it doesn't have builtin requests abort/cancellation.

Sure, sure. You are special and ahead of Flutterfire issues: https://github.com/firebase/flutterfire/issues/10353

The lack of full native Dart support, slow build times, sketchy workarounds, and no desktop support led me searching for another solution. After many hours of research, I was faced with the choice between two frameworks: Appwrite and Supabase. Both were great frameworks and both fit my use case perfectly. But, I decided to move forward with Supabase because of their philosophy of “ not reinventing the wheel”.

For the moment, the pre-compiled SDK doesn't work with the latest flutter firebase libraries: https://github.com/firebase/flutterfire/issues/9761 So it takes an hour to build my project in GitHub action. I can't live with it!

You could write your own bash script or CLI to help manage these tasks. However, this costs you some time. In order to deal with these tasks more quickly, you can use community tools, like Melos, Very Good CLI, or Sidekick. In this article, we are going to use Melos. Melos is also used by repositories like FlutterFire, AWS Amplify (Flutter), Flame, and Plus Plugins.

In the comparison, we focus more on the Sharezone app because Sharezone is a real production app with +300,000 registered users. It uses a bunch of dependencies, like many of the Firebase packages and several other ones (Sharezone is open source — you can find all the dependencies here). Therefore, you will see very realistic build times.

Flutter Fire is the name given to the plugins that integrate Firebase within a Flutter app. There are basically two ways to integrate Firebase into a Flutter app: integration via configuration files, which is done in the native parts of the app, or a newer automated and faster mechanism that was created recently. In this tutorial we are going to use the latter, to do so you have at your disposal an exhaustive explanation in the official documentation, where basically they ask you to install Firebase CLI on your system, and then enable FlutterFire CLI.

Either https://github.com/flutter/flutter/issues/new or https://github.com/FirebaseExtended/flutterfire/issues/new/choose

https://github.com/FirebaseExtended/flutterfire.git, then copy the example folder here: /flutterfire/packages/firebase_auth/firebase_auth/example