-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Analytics #182
Comments
Note that when this is implemented there needs to be a section put back into the index.md to match the FAQ query in Cocoa about MixPanel. |
Karson noted this should log filenames they attempt to open, in the context of the discussion over "default.realm" causing exceptions for migrations needed, when people make minor schema changes and recreate the default instance. |
Our current It is very likely some people using Xamarin will have Xamarin Insights active because it is both free and added by default to new Xamarin projects. Proportionally, I suspect more apps will have Insights than native apps use third-party analytics packages. I feel we should investigate to make sure we can safely have mixpanel and Insights in the same app, on both Android and IOS, before releasing a version with our mixpanel calls. |
Our MixPanel analytics are done at build-time, right? I doubt that will interfere with people using Xamarin Insights which I assume is run-time only. |
Realm collects anonymous analytics when your app is run with a debugger attached, or when it runs in a simulator. (in FAQ ) Nope, not build time. |
Oh, I got that wrong then. But I still don't see how they could possibly interfere? |
I have experience interference in the past with both Crashlytics and Flurry in the same native IOS app. It depends on how they are configured and in particular on who gets to report app crashes - it's a bit Highlander ish |
Ah right, if we are tracking crashes. Yes, that might need some research. |
The main point is that we are vulnerable to whatever configuration that the user puts in their Insights and at the very least should ensure that both default and common configurations don't result in weirdness. It is usually fairly binary - things either work or you get startup errors. |
Brian confirms that build time analytics are sufficient, which is what they do for Android at the moment. |
It would be very useful if we could capture which IDE they are using to build and preferably host OS and target. |
As just discussed in the Product Features Chart review - we should try to implement in the Fody Weaver so it's guaranteed to be at build time. |
implemented in #433 |
Like the RLMAnalytics in Cocoa - this is required before release so we can track adoption. May generate multiple issues depending on how hard it is to do across platforms.
The text was updated successfully, but these errors were encountered: