LEARNED · 2026-10
Why the 3D ran in slow motion on phones
The graphics were not too heavy. Three small choices in the code made a transformation take 19 seconds to arrive.
The background is a map of DNT's six areas and the connections between them. Digital Products is connected to Software & AI. Software & AI is connected to Digital Products, Connected Systems, Automation & CTS and R&D. Connected Systems is connected to Software & AI, Automation & CTS and Hardware & Machines. Automation & CTS is connected to Software & AI, Connected Systems and Hardware & Machines. Hardware & Machines is connected to Connected Systems, Automation & CTS and R&D. R&D is connected to Software & AI and Hardware & Machines. This page belongs to Digital Products and R&D.
Hypothesis
The parts on our pages changed from code to metal far too slowly on a phone. The obvious explanation was that a phone's graphics card is too weak. We wanted to know whether that was true before turning the quality down.
Setup
Phone emulation on an ordinary laptop: 390 x 844 at triple scaling. We measured one part, the fourth in the row, for 26 seconds, reading the transformation's value directly from the calls to the graphics card, so the result did not rest on the eye. Then the same measurement with frames at least 250 ms apart, as on a weak device.
Evidence
Before: first transformation after 19.4 seconds, and one in 26 seconds. After: first after 4.0 seconds, and six in 26 seconds. With 250 ms between frames: none before, six after.
Result
The explanation was wrong. Three things in the code were to blame: transformations took turns among all six parts, including those off the screen; the time per frame had a ceiling, so a slow device ran at reduced speed; and every part woke long before anyone scrolled to it. Now a part wakes when it is seen, and only visible parts transform. Tested on a real phone afterwards, it works there too.
What we learned
Measure before cutting. A ceiling meant to prevent a jump turns a slow device into slow motion, and anything that runs in turns must count only what can be seen. None of it shows on a fast computer.