TireBuddy Integration Guide

Initialize each SDK

• Initialize Tire Tread SDK first, then Mobile SDK.
• Do both once, early in the app lifecycle.
• Do not re-initialize on normal foreground and background transitions.
• Only re-run setup if credentials changed or the initial attempt failed.

Relevant documentation: Flutter plugin getting started. React Native tire tread component.

Set up cloud authentication via Auth Proxy

• For production, keep your client credentials off-device and use a backend-managed token flow.
• We recommend authenticating through the Anyline Auth Proxy to obtain a Bearer token for Cloud API features (Tire Sidewall, Odometer, Enrich).
• Request a token by calling:
  POST https://auth-m2m.anyline.com/api/token?api=<your-api-identifier>&client=<your-client-id>
  The response contains an access_token to use as a Bearer token in subsequent Cloud API calls.
• Tokens are valid for 24 hours. Cache the token and request a new one only when it has expired; do not fetch a new token on every scan or session.

# Get Auth0 Token (Cloud API)
@api=cloud-api
@client_id = <your-client-id>
POST https://auth-m2m.anyline.com/api/token?api={{api}}&client={{client_id}}

# Get Auth0 Token (Insight API)
@api=insight-api
@client_id = <your-client-id>
POST https://auth-m2m.anyline.com/api/token?api={{api}}&client={{client_id}}

Relevant documentation: Cloud API getting started.

Combine VIN and barcode in one flow

• Use a parallel-first VIN and barcode configuration when both are needed.
• Reject candidates that are not 17 characters long after extraction.
• Reject candidates containing O, I, or Q.
• For 18 or 19 characters, strip the first character and keep the next 17.
• For 20 characters, strip the first two characters and keep the next 17.
• For longer payloads, try the first 17 characters as a fallback.

Relevant documentation: Android VIN · iOS VIN · Android barcode · iOS barcode.

Implement sidewall capture guidance

Treat sidewall capture as a guided flow, not a generic camera screen. Users should get clear positioning feedback before they take the image, not only after upload fails.

On the capture screen

• Use a dedicated camera screen with a circular overlay, angle indicator, flash control, and manual capture.
• Keep accelerometer-based angle guidance so users align the phone before capture instead of relying on camera preview alone.
• Validate the angle before allowing upload, and warn the user when the capture geometry is poor.

After capture

• You can persist the captured image if it needs to be available later, for example for inspection history or local report generation.
• For Cloud API image-upload requests, we recommend gzipping the JSON request body and sending Content-Encoding: gzip so large image payloads upload faster.

Recommended implementation reference: Tire Sidewall capture guidance KB article.

Relevant documentation: Tire Sidewall OpenAPI · Tire Sidewall data extraction · gzip Compression for Cloud API.

Apply camera implementation guardrails

These guardrails reduce the capture errors most teams see when sidewall guidance is too loose.

Camera setup

• Use the platform's standard camera API. The Flutter reference app uses the camera plugin. In React Native, react-native-vision-camera is the recommended equivalent. Disable audio capture and initialise without it.
• Open the back camera, request the highest available resolution preset, and fall back progressively (for example: max → ultraHigh → veryHigh → high) if initialisation fails. Retry up to three times with a short backoff before surfacing an error.
• Put a 10-second timeout on initialize() and a 5-second timeout on the "list available cameras" call. Unresponsive cameras should surface an error dialog and return the user to the previous screen, not hang the capture.
• Immediately after initialize(), lock capture orientation to portrait. Do this on the camera controller itself, not just through system orientation preferences, so the preview and the cutout stay stable even if the device is rotated.

Preview rendering

• Most native camera APIs, including the Flutter camera plugin, report preview dimensions in sensor (landscape) space. To avoid a stretched preview and a captured image that does not match what the user saw, render the preview inside a box with the reported width and height swapped, then scale to fit the screen width. react-native-vision-camera handles preview aspect ratio internally, so no manual width/height swap is required. Use its resizeMode prop to control how the preview fills the screen.
• Keep auto focus and auto exposure on by default. A simple tap-anywhere gesture that re-asserts auto focus and auto exposure is enough; you do not need to convert tap coordinates into focus points.

Flash and error handling

• Show a flash toggle, default off. Guard the toggle: if setFlashMode throws on a device that reports no torch, hide or disable the button rather than leaving the user in a broken state.
• Report camera initialisation failures and sidewall scan exceptions to your crash reporter. On sidewall scan failure, re-show the onboarding cards the next time the user enters the capture screen so they are re-oriented on framing and angle before retrying.

Recommended implementation reference: Tire Sidewall capture guidance KB article.

Add tire-size scanning

• Add the Tire Size scan config to the tire flow.
• Default the Tire Size scanner to landscape orientation. The defaultOrientation property applies to cross platform plugin only. For native iOS and Android integrations, lock the screen to landscape orientation in your app code before starting this scanner.
• Default the torch / flash to on for this scan.

Relevant documentation: Android tire size · iOS tire size · iOS UI feedback configuration.