The real work starts after launch
I love building apps. Things become demanding once real people use them.
Then an email arrives: something is broken, confusing or missing. Sometimes it is simply a kind note. I value those messages because someone has clearly spent real time with what I built.
A short report can lead to a long search. The message is in my inbox, the error is in Sentry, the affected session is in PostHog and the code is on GitHub. Before I can solve anything, I have to reconstruct the story.
That became painful across several apps. It was the start of Loopback.
One thread for the whole piece of feedback
I pictured one place showing:
- what the person reported
- what happened technically at the same time
- which part of the product was affected
- what I changed
- whether and how I replied
Loopback connects GitHub, PostHog, Sentry and Stripe. A small button inside the app accepts bugs, requests, criticism and praise. Loopback gathers the context that might help me understand each message.
I can pass that context to Claude, investigate the error, prepare and test a change, then draft a reply. I edit it and tell the person what became of their feedback.
That is where the name comes from: a message reaches me, and a useful answer should make its way back.
Feedback from people who never write
Not every problem produces a message. Sometimes someone signs up, leaves during onboarding and never returns.
For those situations, I can define when Loopback should ask a question. If the person answers, the reply appears inside the right project alongside the usage context.
Those messages must not feel like automated forensic work. I am still working on the timing, the question and a tone that fits the conversation.
Where Loopback stands
The main integrations and the feedback button work. Loopback can collect context, pass it to Claude, contact selected groups and attach replies to the right project.
The open work is mostly about keeping order from turning into a different kind of mess:
- missing context for hard-to-reproduce bugs
- similar reports that belong together
- simpler setup for integrations
- clarity across several projects and many messages
Loopback is not publicly available yet.
Built with
- Next.js
- React
- Tailwind CSS
- Supabase
- Claude Agent SDK
- GitHub App
- Inngest
