Start adding Firebase Auth example

[aritchie]

Should we start thinking about the native naming convention to save on the nuget naming now path length issue? All things firebase, get FB... in this case FBAuth?

[vhugogarcia]

I would like to personally thank you @Redth and @aritchie for providing the slim bindings from Firebase. This is HUGE at least for my projects personally. Since yesterday, I spent a few hours, understanding the architecture, reviewing the README.md file and I even ran some local tests on macOS for Firebase Analytics and it worked very good on the initial tests.

I will continue running tests on my local now for the Firebase Messaging, confirming it works also as expected on my side, and also I will review and learn the XCode projects, to learn about it and see if I can contribute to this repository as well somehow 😃

With your permission @aritchie , about the naming convention, I believe, if that in the past the bindings for firebase iOS they were for example: Xamarin.Firebase.iOS.Analytics, I believe we can try leaving as Firebase.Auth looks good for simplicity, however, there is already a package on NuGet with that name, so if not possible, then another option may be:

• FIRAuth
• FIRAnalytics
• FIRMessaging
• FIRFunctions
• FIRFirestoreDatabase
• FIRRemoteConfig
• FIRCrashlytics
• FIRStorage

FIR stands for Firebase, and even Google officially name them with the prefix FIR on their iOS code, I'm not sure why honestly. hehe!

I just wanted to share my grain of salt! I'm up to what you decide it is better 😄

As additional information, Firebase will end support of a service such as:

• Dynamic Links is no longer supported, and will stop working on August 25, 2025.

[pjcollins]

Closing this, I've folded these changes into https://github.com/Redth/DotNet.Platform.SlimBindings/pull/25.