{"id":36024,"date":"2026-05-30T10:24:00","date_gmt":"2026-05-30T08:24:00","guid":{"rendered":"https:\/\/harlerunner.de\/?p=36024"},"modified":"2026-07-11T15:58:55","modified_gmt":"2026-07-11T13:58:55","slug":"loop-ui-why-i-built-my-own-interface-for-intervals-icu","status":"publish","type":"post","link":"https:\/\/harlerunner.de\/en\/loop-ui-why-i-built-my-own-interface-for-intervals-icu\/","title":{"rendered":"Loop UI \u2014 Why I Built My Own Interface for intervals.icu"},"content":{"rendered":"\n
<\/div>\n\n\n\n

intervals.icu can do a lot \u2014 it’s just that the interface looks like it was built for data, not for checking in every day. My training is planned elsewhere anyway, through an AI assistant; for me, intervals.icu mainly manages the data and pushes the workouts to my watch. So I packed the features I actually need daily into my own tool: “Loop UI.” A single HTML file, my plan in magazine style, live-connected to the real account \u2014 plus a few analyses that don’t exist anywhere else.<\/strong><\/p>\n\n\n\n

<\/div>\n\n\n\n

Note:<\/strong> loop isn’t a product you can buy or download \u2014 it’s a private hobby project for my own plan, behind a password. So this article isn’t a review to go shop for, but a workshop report \u2026 ;)<\/em><\/p>\n\n\n\n

\n
\n\n\n\n

Loop UI<\/h2>\n\n\n\n
\n
\n

Type<\/strong><\/p>\n\n\n\n

Self-built \u2014 a standalone HTML file, also runs offline<\/p>\n<\/div>\n\n\n\n

\n

Base<\/strong><\/p>\n\n\n\n

intervals.icu as the data hub, live via the API<\/p>\n<\/div>\n\n\n\n

\n

Access<\/strong><\/p>\n\n\n\n

Locally by double-click \u2014 or online, even from a phone<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n<\/div><\/div>\n\n\n\n

Loop UI: a self-built browser interface for my own intervals.icu plan, made for data-loving hobby runners. Not a product to buy, but a private tool \u2014 able to run offline, though for me it’s reachable online too, even on mobile. Five views, from the weekly cockpit to the season overview, plus an HRV analysis based on Plews that doesn’t exist anywhere else. Anyone who’d rather read their plan than manage it will get the appeal right away.<\/p>\n\n\n\n

\n\n\n\n

Why build a custom interface at all?<\/h2>\n\n\n\n

intervals.icu<\/a> is a Swiss Army knife \u2014 powerful, dense, a bit technical. The calendar shows everything, but it doesn’t exactly invite you to just glance at it over morning coffee. That’s exactly what I wanted though: a tool I’d actually enjoy opening \u2026 not one I have to work my way through.<\/p>\n\n\n\n

On top of that: my training isn’t even planned in intervals.icu \u2014 it’s planned through an AI assistant (Claude)<\/a>. For me, intervals.icu is the data hub \u2014 it stores, evaluates, and pushes the workouts to my watch. Whatever I actually need to see day-to-day, I’ve gradually pulled together into loop.<\/p>\n\n\n\n