firebase (AngularDart) vs cloud_firebase (Flutter)

[Bruce Abernethy]

I'm sure this has come up before, but I didn't find it when searching.

It'd sure be nice if the AngularDart and Flutter implementations of some of the firebase code shared an interface/abstract class at some level.

Both have a "CollectionReference" and "DocumentReference" but the methods and parameters aren't consistent and able to be abstracted.

For example in Flutter DocumentReference has a "documentId" and in Angular it is just "id" - in Flutter it is "setData" in Angular it is just "set"

In CollectionReference Flutter has "document()" in Angular it is "doc()".

It's cool that these changes are very easy to change, but it is one more module (the repository) that I need to manually maintain an Angular and Flutter version in Dart.

It is great that all the Dart models move smoothly between the two (if I avoid "TimeOfDay" that is conspicuously only in Flutter).

I know making this run in the Flutter/mobile/native environment must be vastly different than making it work in the browser/javascript environment - it's amazing so much works well between the two.  But if these could get even closer in the future, it would save even more time and lead to less code to maintain.