← All work

One-click diagnosis for mobile app connection failures

Turned the slowest, most log-heavy mobile app tickets into a one-click diagnosis for a support team.

01 Problem

Store owners kept reporting the same one-line problem: “the app won’t load” or “it says not connected”. The store worked fine in a browser, the app’s error message rarely matched the real cause, and every ticket meant reading long app logs by hand before replying.

02 What I did

I read the app logs on 21 of these cases and found that almost all of them fit one of five patterns: a CDN or firewall blocking the platform’s servers, a slow or unreachable host, a PHP fatal error on REST routes, an expired connection token that looks like a disconnected site, and a blocked login. Each pattern has its own signature in the logs. I wrote these up as a guide for the team, then turned the checks into a Chrome side panel. One click reads the app’s status report and logs, runs connection checks, and names the likely cause, the evidence and the next step.

03 Result

A diagnosis that used to take a careful read of several logs now starts with one click. The guide became the team’s reference for these tickets, and teammates cite it in their own write-ups. Next: collect feedback from the test round and turn it into better detection rules.

Have a problem that keeps coming back?

I reply within one working day.