Replies: 2 comments 2 replies
-
The biggest advantage is that you use the native SDKs. A few examples:
|
Beta Was this translation helpful? Give feedback.
-
Ok thanks for this answer. I guess I didn't think of the first few you mentioned, like the big Auth capabilities which I am using and which are super nice for me to use. I failed to phrase my what I am wanting to know correctly. Really I was only looking for explanantion for firestore. I do not use other libraries but firestore & auth, so do not know abotu the other ones. But as a final feedback: not in this main section: nor in the specific section: For auth it was clear what is adds for me since it was what I was looking for. But not for firestore. but maybe I did not read the docs well enough. idk about other library parts, where a purpose docs would be good. Thank you for this library again. I hope you can make use of my feedback somehow |
Beta Was this translation helpful? Give feedback.
-
All I can find is:
🦋 Consistent versioning (no more SDK versions conflicts)
👁 Unified Typescript definitions
📄 Full documentation
Is this all the benefits this library provides?
Maybe some more info would be good, like what exactly should convince me to use this abstraction instead of going with the bare web-js sdk or the angular/fire library?
Probably the initial setup is easier, since this plugin adds configs to the native app folders. But other than that, is there benefits? Would be interesting to find out
Beta Was this translation helpful? Give feedback.
All reactions