The Avo Inspector SDK is designed to be small and easy to include in any project.
Table of Contents
Find in the Avo Inspector overview guide.
In order to ensure our SDK doesn't have a large impact on performance or battery life it supports event schemas batching. In production, default values are 30 schemas per batch and smaller batches are sent if more than 30 seconds pass between uploads.
In development batching is disabled by default.
You can change the values using
AvoInspector.setBatchSize(newBatchSize: Int) and
AvoInspector.setBatchFlushSeconds(newBatchFlushSeconds: Int) class methods to fine tune the library performance.
When initializing the Inspector SDK you'll be prompted to provide the current app version. Providing correct app version is not required, but doing so significantly improves the Inspector issue reporting. By providing app version the Inspector is able to tell in what version an issue was first seen, and in what version the issue was fixed. Versions also allow the Inspector to report more accurately on the implementation status of your events, by focusing on the implementation status in your latest app version for every source.
We recommend using semantic versioning (e.g. "1.0.0") or other types of numeric versioning (e.g. build number) which get incremented on every release.
Examples of great app versions, incremented with every feature release:
Examples of bad app versions:
Don't have versioning for your app in place? Reach out to us and we'll help you set up versioning in your app.
If you are using Segment Analytics for tracking integrating Avo Inspector SDK is even easier.
We provide a code snippet to be used as middleware component that you supply to Segment during initialization. That will allow Avo to analyze schemas of all event tracked by Segment.
Check platform docs for more information and actual code snippets.