Our own product
ifishlog: a broken app, brought back to life
ifishlog is a personal outdoors-logging app — a single user, so this isn't a traction story. It earns its place for what happened when the app died: a third-party weather provider it depended on was deprecated, the external API went away, and the application simply stopped working. Dependency rot — the classic way aging software dies, not from a bug you wrote but from the ground shifting beneath it.
What changed
We pointed our agentic pipeline at it. The agents diagnosed the failure, replaced the dead dependency, and revived the application — a broken, non-functional app back to working order, then back into continuous development.
Broken → revived
A dead app diagnosed, its rotted dependency replaced, and brought back to working order.
Not a rewrite
Rescued in place — no write-off, no start-from-scratch.
Every aging application is one vendor deprecation away from breaking, and fixing that rot is the unglamorous work that never gets prioritized until it's an emergency. If a vendor change has quietly killed something you rely on, it's recoverable.