The use Crashlytics should be abstracted away seening as it's an implementation detail. Abstracting Crashlytics should also make it possible to have someone use their own custom logging solutions. Perhaps an event bus driven approach would be suited better in this case. This way the developer could for install several listeners to for example log to the disk, a custom API and or Crashlytics.
The use Crashlytics should be abstracted away seening as it's an implementation detail. Abstracting Crashlytics should also make it possible to have someone use their own custom logging solutions. Perhaps an event bus driven approach would be suited better in this case. This way the developer could for install several listeners to for example log to the disk, a custom API and or Crashlytics.