Triagepad reads your beta feedback, localises each report against your real code, and hands you a fix ticket that points to the file and line. Delivered as a plan, an open PR, or an auto-fix.
You ship through TestFlight, testers send whatever they feel, and it lands as a heap of context-free notes. You triage it by hand, lose the thread, and real bugs slip through between builds.
No steps, no build number, no idea which screen. You reproduce it by guessing.
打开个人资料就闪退
A tester reports in their own language. Bug or feature request? You can’t tell. You can’t even read it.
Duplicates across builds bury the one report that actually matters. Nothing is grouped.
A note scrolls off, a request is forgotten, a fixed issue keeps getting re-reported. No trail.
Link your App Store Connect account and point Triagepad at the GitHub repo behind the app. Self-serve setup takes about five minutes.
A tester submits feedback and Triagepad localises it against your code, running inside your own CI. Candidates are ranked and verified at HEAD.
Receive it as a plan, an open PR, or an auto-fix, with the file and line already pinpointed. Review and merge.
Left: what the tester actually sent. Right: what Triagepad found in your code, with ranked candidates verified against HEAD and a fix prompt ready to run.
“Když otevřu profil z odkazu v e-mailu, aplikace hned spadne. Přes záložku profil funguje normálně.”
“When I open the profile from a link in an email, the app crashes immediately. Through the profile tab it works fine.”
Opening a myapp://profile URL with no userId query force-unwraps a nil value, raising a fatal error before the view appears.
Triage runs inside your own pipeline. The Triagepad brain only ever triages feedback that has already been collected, and it mints a short-lived token to do it. Your repository tree is never sent to Triagepad, and never stored.
What comes back is the ticket: the ranking, the file and line references, the fix prompt. The code stays where it always was.
Localisation happens on your infrastructure. The tree is read where it lives.
The brain gets a scoped, expiring token to triage collected feedback. Nothing persistent.
Runs on your own Anthropic key from your repo secrets. Triagepad never touches it.
Plan, open PR, or auto-fix. You pick the automation level per app. Schema and design-decision tickets always wait for you.
Feature requests surface, fixed-stale reports are detected, and needs-decision tickets are gated. Nothing scrolls into the void.
Watch a ticket move from triaged to open PR to merged, with the evidence source recorded when it resolves.
Self-serve. Connect App Store Connect and your repo, and Triagepad starts triaging the next feedback that lands.
We’re onboarding indie developers and small teams by invite. Request access and we’ll be in touch. Free during the beta.