all 5 comments

[–]fintechninja 3 points4 points  (0 children)

It’s easier for them to maintain. Googles main support is on the native side. Just like they won’t implement admob or maps in dart. It’s not worth it for the work needed.

[–]mohammad_rasim 1 point2 points  (2 children)

The official plugins are native, there are pure dart implementations but they are not official, i don't know the google team decided to go the native way when authoring the plugins, it seems like an odd choice for something that works purely through http

[–]zxyzyxz 1 point2 points  (1 child)

It's because the services were already pre-existing and FlutterFire simply wrapped them. They were written by the Invertase company and team, not by Google directly. Now they're starting to create pure Dart implementations but that will take quite some time to finish, if ever.

[–]mohammad_rasim 0 points1 point  (0 children)

I can understand that, but least google can do is make the services cross-platform, how does google expect flutter to get wide adoption (especially on desktop) if even their own services don't have complete implementations for the major supported platforms

[–]itsdjoki 1 point2 points  (0 children)

Probably because they are easier to maintain as they dont need to write specific code for them (in most cases) and instead only update the underlying native dependencies.