You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the spirit of not reinventing the wheel, why not integrate these backends into an open source (and personally I think a great library) project ACRA within their backends.
This might (hopefully) force those providers you have in your library and similar to utilize ACRA as the interface to tracking/analytics. Just my .02 cents. Thanks.
The text was updated successfully, but these errors were encountered:
@sahal2080 ACRA is a great service. It's a fantastic crash reporting tool. Foam does a bit more than ACRA in that it tries to make it easy to setup not only crash reporting, but some of the other things you should have in place before you publish an app; event tracking and remote logging. Also, it looks like for crash reporting, ACRA already provides integrations with the same services that Foam does (and a few more) so I don't think porting foam backend integration code to ACRA is actually needed. If someone just wants crash reporting ACRA is a good solution. If they are also looking for analytics and remote logging, Foam could be used. The 2 are also not mutually exclusive.
In the spirit of not reinventing the wheel, why not integrate these backends into an open source (and personally I think a great library) project ACRA within their backends.
This might (hopefully) force those providers you have in your library and similar to utilize ACRA as the interface to tracking/analytics. Just my .02 cents. Thanks.
The text was updated successfully, but these errors were encountered: