App Analytics

[anuraagbaishya]

Currently the app does not use any method to analyse crashes. Crash Analysis can be added for greater insights about the functioning of the app.

[kartikarora]

We can add that, what do you suggest?

[kartikarora]

I've updated the title to include not just crash analytics but all kinds of analytics. We can go with New Relic or use the Parse one.

[anuraagbaishya]

That should do. Also we can try Fabric

[kartikarora]

Fabric is limited to crash analysis, and the dashboard is a bit sophisticated. Have a look at new relic and parse analytics. If required, I'll make an LUG account and give the credentials.

[anuraagbaishya]

I'll have a look.

[AniketSK]

@kartikarora There's an import for parse but according to their website, their service was shutdown and support will be cancelled. Moving to another service will be required. Would you want to stay with new relic or are you ok with Crashlytics/Firebase now?
Just checked new relic, is it just paid now? And steeply paid at that.

[kartikarora]

Oh dear didn't know this was still up.

I guess we can skip new relic. Actually now we need to completely migrate to a nee backend, and rebuild the app from scratch. If you're up for the herculean task, lets discuss it further.

[AniketSK]

@kartikarora let's do it man.

[kartikarora]

Awesome. I was thinking of firebase as the sole backend. I can setup the app from the console and push an update.

[kartikarora]

@AniketSK Also give me your debug keystore's SHA-1 so that I can setup it up on firebase!

[AniketSK]

36:08:B1:D0:01:3E:84:0F:99:22:6E:D6:53:2B:BB:CB:C5:82:A5:DF

Though you could just add your debug keystore to the project and configure it to build with that for debug if you prefer :)

[kartikarora]

I'll add both, so that it works on your device as well!