Developers
One provider around your app. That is the integration.
Install the package, put one provider around your navigator with the embed key an admin creates in TickFlow, and add breadcrumbs where they help. Your logging and crash reporting keep working exactly as before.
- Trail runnerSize 9 · Blue$129.00
- Running socks3 pack$18.00
TF-8F42-QKDoneReact Native & Expo Available
Three steps. Then shake.
For React Native and Expo apps (Expo SDK 54 or later). The code for each step is in the setup guide and the technical briefing.
- step 1Add the packageYour TickFlow contact sends the package and a setup guide. It installs like any React Native or Expo dependency, alongside a few standard native modules.
- step 2Wrap your app onceOne provider around your navigator, with the embed key an admin creates in TickFlow and the app id you allow. A single switch keeps it to internal, QA and beta builds.
- step 3Add context where it helpsBreadcrumbs, the signed-in user and a "Report a problem" menu item are one line each. Without any of them, a shake still opens the report.
Good to know
The questions developers ask on day one.
- Where the provider goes
- Inside your other providers, around your navigator. The screenshot is of the provider’s view, so wrap the whole app.
- Expo Go works
- The native modules it uses are bundled in Expo Go. Pass appId explicitly there, because Expo Go reports its own id.
- Shaking in development
- In dev builds a shake also opens the Expo developer menu; release builds show only the report card. In the iOS Simulator, use Device → Shake or open it from your own menu item.
- Which network calls
- Calls made with fetch are recorded. Libraries that bypass it, such as axios, are not: add breadcrumbs from an interceptor if you need them.
- Optional modules stay optional
- Without the screenshot module a report is sent without a screenshot; without the sensors, opening it from a menu item still works. The app never crashes for a missing one.
- Your logging is untouched
- Console output, LogBox, Metro and your crash reporter behave as before. You can add your own redaction rules for anything app-specific.
Native apps
Android and iOS, in early access.
The native SDKs were built for TickFlow Field. If you want them for app testing, ask us and we will tell you where they stand for your apps.
- KotlinEarly access
Android
A native SDK built for TickFlow Field: app logs, errors, breadcrumbs and context, redacted on the device. Ask us if you want it for app testing.
- SwiftEarly access
iOS
A Swift package with a shake-to-report sheet, built for TickFlow Field and redacted on the device. Ask us if you want it for app testing.
Ready to add it to your app?
TickFlow SDK comes with TickFlow Web plans from $200/month. On one already? Your TickFlow contact sends the package and the setup guide.
Or write to hello@tickflow.co