The SVG was the whole lag

Two bugs, both instructive, both from Severo’s first days actually installed from the Play Store. The first is bureaucratic: audio recording silently refused to work, and the cause wasn’t in the code at all, the Play Store requires a privacy-policy URL configured in the console before the microphone permission functions ▸ 55:58. He’d handled it in code and assumed that was the whole job; the store had a parallel checkbox waiting.

The second is the keeper. The app ran slow, and his first theory blamed the debug harness, USB-tethered execution ▸ 56:26. Then the published version was slow too, which killed the comfortable explanation and forced the differential: of all the app’s pages, exactly one loaded fast, the dashboard, and it was the only page without the Severo mascot SVG ▸ 56:56. The vector was apparently recalculating its layout in a loop, expanding against its container every frame ▸ 57:20. Swap in a PNG, and the whole app comes back to speed.

la página que funciona es un grupo de control; mírala primero →

The transferable move is the shape of the diagnosis: when something is slow everywhere, the page that isn’t is your control group, and the difference between it and the rest is a one-item suspect list. He didn’t profile, didn’t guess at the framework; he subtracted. That, and the meta-lesson this arc keeps paying for: half of mobile development lives outside your codebase, in consoles with checkboxes that fail silently…