How it works
One shake. One ticket. No “can you send a screenshot?”.
Step through one report from a beta build: what happens on the phone, what arrives in TickFlow, and who is in control at each point.
- Trail runnerSize 9 · Blue$129.00
- Running socks3 pack$18.00
TF-8F42-QKDoneStep through it
One report, start to finish.
Use the tabs or the arrow keys. Each step shows the phone, TickFlow and who is in control side by side.
- On the phone
- The SDK keeps the recent console lines, JavaScript errors, network calls and your breadcrumbs, from the moment the app starts. Secrets and e-mail addresses are replaced as each value is captured.
- In TickFlow
- Nothing. Nothing leaves the phone until someone sends a report.
- Who is in control
- You. One switch decides which builds include it at all: internal, QA or beta. Switched off, it does nothing.
14:31:52 [LOG] Navigated to Checkout 14:31:53 [LOG] GET https://api.shop.example/cart?session=[redacted] 14:31:58 [LOG] Receipt e-mail set to [email] 14:32:01 [LOG] POST /checkout Authorization: Bearer [redacted] 14:32:02 [WARN] Payment request failed, status 502 14:32:02 [ERROR] TypeError: Cannot read property 'id' of undefined
Before the first report
Three steps, one of them in TickFlow.
- 01
Allow the app
In TickFlow, an admin opens Collect Feedback for the client account, adds the app’s bundle id or package name and creates an embed key.
- 02
Add it to the app
Your developer installs the package and adds a few lines around the app. Your TickFlow contact sends the setup guide.
- 03
Shake to report
Testers shake the phone, check what will be sent, add a few words and send. The ticket arrives with the evidence attached.
The same embed key can serve a client’s website feedback widget and their app.
In your app
A few lines in your app. Nothing else changes.
Only in the builds you choose
One switch keeps it to internal, QA or beta builds. Switched off, it does nothing at all.
Shake, or a menu item
Shake detection is on by default. Turn it off and open the same card from a Report a problem item in your own menu.
Your logging keeps working
Your console output and crash reporting behave exactly as before. Add breadcrumbs and context where they help.
See a report land in your own TickFlow.
TickFlow SDK comes with TickFlow Web plans from $200/month. Talk to us, or upgrade your plan, and your testers can shake to report.
Or write to hello@tickflow.co