{"id":16951,"date":"2026-01-23T19:55:23","date_gmt":"2026-01-23T19:55:23","guid":{"rendered":"https:\/\/blog.tubikstudio.com\/?p=16951"},"modified":"2026-04-06T12:12:57","modified_gmt":"2026-04-06T12:12:57","slug":"netti-case-study-measuring-the-invisible","status":"publish","type":"post","link":"https:\/\/tubikstudio.com\/blog\/netti-case-study-measuring-the-invisible\/","title":{"rendered":"Netti Case Study: Measuring the Invisible"},"content":{"rendered":"

Most apps tell you what to do. Netti made the one that tells you what’s wrong.<\/span><\/p>\n

It measures connection speed in real time\u2014download, upload, ping, jitter, signal strength. One tap, and your internet starts confessing\u2014speed fluctuations, bad routing, latency spikes. Suddenly, you\u2019re staring at a bunch of numbers that feel less like metrics and more like a system having a nervous breakdown.<\/span><\/p>\n

And that\u2019s where we came in. Our job was to make that breakdown readable. Make the chaos make sense. Design a tool that doesn\u2019t just show the problem\u2014it explains it.\u00a0<\/span><\/p>\n

And that\u2019s exactly what we did.<\/span><\/p>\n

\"\"<\/p>\n

The Ask: Make the Invisible, Visual<\/span><\/h2>\n

Netti came to us with a bold idea: a mobile app that could measure internet connection performance in real time\u2014and explain it in a way that anyone could understand. Not just tech bros in their server caves, but your dad testing his new router, your neighbor troubleshooting their streaming, your average user wondering if the lag is <\/span>them<\/span><\/i> or the world.<\/span><\/p>\n

Speed test apps existed, sure. But most of them treated you like a modem, not a person. Netti needed to be smarter than that.<\/span>
\n<\/span>It had to be honest, but not harsh. Technically credible, but never cold. Intuitive to use, even if you didn\u2019t know what half the numbers meant.<\/span><\/p>\n

Our challenge was clear:<\/span>
\n<\/span>Translate a machine\u2019s language into something human.<\/p>\n

Research & Strategy: Listening Before Designing<\/span><\/h2>\n

We started by doing what any design team does when faced with technical complexity:<\/span>
\n<\/span>We listened.<\/span>
\n<\/span>To users, to competitors, to the engineers behind Netti.<\/span>
\n<\/span>To that small, persistent voice that says, \u201cI don\u2019t get what this number means\u2014should I be worried?\u201d<\/span><\/p>\n

Our researcher Natalka Mamchur mapped out the playing field\u2014what users expect from internet test apps, where current ones fail, and what kind of feedback loops we could build into the experience.<\/span><\/p>\n

Then we got to work defining flows. Where do users land? When do they start drowning in data? How far can we take them without needing a glossary?<\/span><\/p>\n

Each answer became a post-it. Each post-it became a screen. Each screen had to do one job: make the data feel like a story, not a spreadsheet. For this case, we needed to build a system that knew when to explain\u2014and when to stay silent.<\/span><\/p>\n

\"\"<\/p>\n

UX\/UI Design: Turning Numbers into Interaction<\/span><\/h2>\n

Anastasiia Zhyltsova led the interface design\u2014both for the app and the launch website. She treated the numbers not as outputs, but as characters. Each metric had its own temperament, its own place in the story.<\/span><\/p>\n

While plenty of speed test tools already existed, most stopped at surface-level stats. Netti went further. It offered real-time access to deeper diagnostics: traceroutes, data throughput, local network info. Serious tools, typically buried behind command-line walls, now packed into a clean mobile UI.<\/span><\/p>\n

The challenge was to make all of that complexity readable. Not only for the pros\u2014but for the rest of us, too.<\/span><\/p>\n

\"\"<\/p>\n

So before a single pixel was pushed, we built the bones. Wireframes, flows, scenarios. We walked through use cases like we were debugging a system in real time\u2014testing logic, trimming steps, flagging points of confusion before they could turn into friction. The back-and-forth here was steady and detailed. Not glamorous, not fast, but absolutely necessary.<\/span><\/p>\n

Once the logic clicked, we moved into the visual layer\u2014shaping a system that felt sleek without trying too hard, distinct without distracting. Accent colors gave us anchors: clear calls to action, visible touchpoints, visual rhythm. Navigation was stripped down to a single home screen\u2014no bottom tabs, no hidden drawers. Everything up front, ready to go.<\/span><\/p>\n

Tap a service, and you land on a focused screen with a single goal: run the test. The central animation doubled as both anchor and indicator\u2014quietly tracking progress without shouting for attention.<\/span><\/p>\n