Skip to content
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

Closed
AndyDentFree opened this issue Nov 9, 2015 · 13 comments
Closed

Implement Analytics #182

AndyDentFree opened this issue Nov 9, 2015 · 13 comments
Assignees
Milestone

Comments

@AndyDentFree
Copy link
Contributor

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.

@bmunkholm bmunkholm added the P1 label Nov 17, 2015
@AndyDentFree
Copy link
Contributor Author

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.

@AndyDentFree
Copy link
Contributor Author

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.

@AndyDentFree
Copy link
Contributor Author

Our current RLMAnalytics is based on mixpanel.

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.

@kristiandupont
Copy link
Contributor

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.

@AndyDentFree
Copy link
Contributor Author

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.

@kristiandupont
Copy link
Contributor

Oh, I got that wrong then. But I still don't see how they could possibly interfere?

@AndyDentFree
Copy link
Contributor Author

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

@kristiandupont
Copy link
Contributor

Ah right, if we are tracking crashes. Yes, that might need some research.

@AndyDentFree
Copy link
Contributor Author

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.

@kristiandupont
Copy link
Contributor

Brian confirms that build time analytics are sufficient, which is what they do for Android at the moment.

@AndyDentFree
Copy link
Contributor Author

It would be very useful if we could capture which IDE they are using to build and preferably host OS and target.

@AndyDentFree
Copy link
Contributor Author

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.

@kristiandupont kristiandupont added this to the rc milestone Mar 1, 2016
@fealebenpae fealebenpae self-assigned this Mar 14, 2016
@fealebenpae
Copy link
Member

implemented in #433

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants