Use of plugin as a singleton

[debkanchan]

In this current form, this plugin requires that the user create an analytics instance and use it throughout the app, which requires either

• using a global analytics variable (which is not recommended and is an antipattern)
• wrapping it with a singleton class(inconvenient)
• dependency injecting it (using prop drilling or state management solutions).

Rather than this, it would be beneficial if it was a singleton instance like Segment.Instance just like how Firebase analytics does it with FirebaseAnalytics.Instance

[edsonjab]

Hi @DebkanchanSamadder thank you for your report, we start looking into this and we will check your PR.

[oscb]

Not doing singletons is part of the design of the library to enable support for multiple clients by default. This is better to handle per app at the moment.