Anyline Tire Tread SDK Datasheet v13
Anyline Tire Tread SDK is designed to be integrated into mobile apps on native iOS and Android. It can also be accessed via Instant Apps for iOS and Android. Anyline Tire Tread SDK processes data on the device and in the cloud, thus requires a stable internet connection.
| Tire Tread SDK for Android | v13.0 |
| Tire Tread SDK for iOS | v13.0.1 |
| Tire Tread Plugin for Flutter | v1.2.1 |
Disclaimer
Anyline products are built to deliver fast and reliable data capture solutions. There are however, certain factors that can limit or negatively impact data capture speed and accuracy. These are factors for which we are not responsible and cannot assume any warranty or liability. These include, for example:
- Non-compliance with technical requirements for the specific product and/or module, as set forth in this Datasheet or otherwise agreed
- An unsuitable scanning environment, such as scanning an object under extreme lighting conditions or from a far distance
- Any obstructions on the object that you wish to scan, such as obscured text or a very shiny surface
- The quality of an image you try to scan, for example images that are blurry, out of focus or low resolution images
- Incorrect handling by users, such as using the products with a lack of sufficient experience or unsteady hands (Please read the tire tread how-to-guide on best practices for getting optimal results.)
Thus, the tire tread scanner provides a mere estimate of the tire depth at a given point on the tire. The result of the tire depth measurement does not indicate whether the tire is roadworthy or not. To check the roadworthiness, you need to consult with a mechanic. The results that the tire tread scanner provides only show the depth that the Product has measured. We do not guarantee that this result correlates with reality. The parties expressly agree that no legal consequences may be derived from a result of the tire depth measurement that does not correspond to reality.
Availability
Anyline commits to 99.5% uptime per month for data capture capabilities offered via API. For this purpose, the uptime shall be calculated as follows: (actual availability + excluded periods according to the next paragraph) x 100/maximum availability. The “maximum availability” per month is 24 hours multiplied by the number of days in the respective calendar month. The actual availability is the time during which you have access to the data capture capabilities offered via API. When determining the availability achieved, the following periods in which service provision by the Provider is not possible for the reasons listed below will be deducted:
- Maintenance work, provided that such maintenance work is announced to you through the Anyline Support Status website at least 24 hours in advance, up to a maximum maintenance time of 5 hours per month. To receive notifications, users must subscribe via the page.
- Outages or failures of systems, system components or telecommunications infrastructure of ANYLINE or of third parties acting for ANYLINE in the event such outages or failures are the result of a force majeure event (such as fires, flood, earthquake, lightning strike, pandemics, etc) or events which are outside of the control of ANYLINE
- Malfunctions or failures that are caused, at least in part, by your use of the services in violation of your license agreement or otherwise improperly; this includes, in particular, use of the services outside the area of use specified in the description in the Datasheet, use by untrained personnel or unauthorised third parties, and failure to perform maintenance in accordance with Anyline’s guidelines
Requirements
| iOS | Android | |
|---|---|---|
| Minimum OS Version* | iOS 16.4 (iOS 17 for Instant App) | Android API Level 28 |
| Device Compatibility Mode^ | N/A | Always on |
| Camera Resolution | Minimum: 1080p video camera | Minimum: 1080p video camera |
| Flash | Torchlight feature (continuous flashlight) | Torchlight feature (continuous flashlight) |
| Recommended Phones | iPhone SE (3rd Gen), iPhone 11 and above | Samsung Galaxy A55, Galaxy S10, Galaxy S21, Galaxy S23, Google Pixel 5 and above |
| Recommended Tablets | iPad Mini (6th generation) or better (larger iPads are only recommended for use on unmounted tires or when vehicles are lifted) | Samsung Galaxy Tab Active 3 or better (larger tablets are only recommended for use on unmounted tires or when vehicles are lifted) |
| Internet Connection | - Stable internet (at least 0.5 Mbit/s upload speed) - Recommended at least 15 Mbit/s download speed and at least 5 Mbit/s upload speed for best experience | - Stable internet (at least 0.5 Mbit/s upload speed) - Recommended at least 15 Mbit/s download speed and at least 5 Mbit/s upload speed for best experience |
| Architecture | arm64 / x86_64 simulator | armeabi-v7a / arm64 |
| Recommended Tooling | Latest Xcode | Latest Android Studio |
| Wrappers | Flutter | Flutter |
| SDK Size** | 7 MB | 1 MB |
*Subject to change on a yearly basis. We will always strive to support at least the last 3 releases.
^Device Compatibility Mode enhances tire tread measurement accuracy on Android devices by allowing users to input tire width information
**Actual numbers may vary depending on the platform, operating system and or recognition task
Tire Tread
Capabilities:
- Passenger/Light Vehicle Tires
Specifications:
- Returns results for 3 separate tread areas
- Average accuracy on recommended iOS devices (shown in requirements table above):
- 0.5 mm / 1/32” for remaining tread depth between 1 mm and 10 mm
- Average accuracy on recommended Android devices (shown in requirements table above):
- 0.5 mm / 1/32” for remaining tread depth between 1 mm and 10 mm
- Resolution: Results shown in increments of 0.1mm / 1/32"
- Minimum groove depth: 0.5 mm (1/32”)
- Maximum groove depth: 10 mm (12/32”)
- Results shown for grooves with a minimum width of 5 mm (6/32”)
- Audio and haptic feedback for user guidance
- No support for dual tires