Insights · · Rune Sport · Updated
Designing Rune Sport’s Planning Experience with MadeByCat
How Rune Sport’s planning experience is designed for athletes and coaches: information architecture, interface and web development approach, mobile-first use, accessibility and performance.
Planning context for athletes and coaches
Rune Sport’s digital sports planning experience connects a run schedule with the details needed to choose a session. An athlete can check the city, date, start time, distance, pace and difficulty before opening a run page. A coach can use the same public information to compare listed sessions and share a relevant run with a group; the site does not present a separate coaching workspace or personalised training-plan builder.
The planning flow starts with the run calendar: filter by city, month and difficulty, choose a grid or list view, then open a session. Pace is shown in the session information rather than offered as a separate filter. On the detail page, the runner can review the meeting point, format and session flow, then continue to another listed run or the related kit.
User experience and information architecture
The site is organised into a small number of durable sections: the club story, the run calendar, individual run pages and the kit that supports those runs. Each section has one job, and every page states its own purpose in the first screenful rather than asking the visitor to scroll to find out where they landed.
Run pages are the centre of the structure. Each brings together the meeting point, distance, pace, format and session flow, followed by a gallery and kit section. The gallery is part of the presentation, not evidence of a documented previous edition. Above these pages, the calendar offers image-led grid browsing and a list for comparing session information.
Breadcrumbs keep the hierarchy visible on deeper pages. A runner can move from a session to a product detail, choose an available size and add the selected item to the cart. These links connect planning and equipment browsing without requiring a return to the home page; they do not establish that a product was tested at a particular event.
Interface and web development approach
The interface uses a restrained palette, a single accent colour and a typographic hierarchy that does the structural work: large display headings for orientation, monospaced labels for metadata such as dates, cities and distances, and a neutral body face for reading.
MadeByCat supported the design and development of Rune Sport’s digital experience. The front end is built with React on TanStack Start, with file-based routing, server-side rendering and a shared component layer for navigation, cart and gallery behaviour, so the same patterns repeat across every page rather than being rebuilt per screen.
The shared interface includes section reveals, button interactions and page transitions. These effects sit alongside the practical flow of finding a session, reading its details and moving to a related page; they are not evidence of improved user behaviour or measured performance.
Mobile-first use
Checking a session on a phone is a design scenario, not a finding from documented UX research. The mobile-first UX/UI uses narrower reading layouts and a menu drawer, while preserving the same calendar-to-session and session-to-product paths as the desktop experience.
The home-page gallery becomes a swipeable slider on smaller screens. Calendar controls and session information adapt to the available width so choosing a run and reading its details do not depend on a desktop layout. This article was checked at 390, 820 and 1440 pixels wide; that check does not establish device-wide usability research.
Accessibility and performance
This article uses a main landmark, one H1, section headings and a semantic blockquote with an organisation-level attribution. Meaningful images elsewhere in the experience have alternative text; this text-led article has no content image. The site includes reduced-motion styles, but those implementation details are not a claim of complete accessibility compliance.
The article’s main content and metadata are present in the first server-rendered HTML. Shared font links use preconnect and font swapping, selected links preload on intent, and gallery images use lazy loading. These are implementation choices, not measured loading-speed improvements, Core Web Vitals results or user-performance metrics.
Müşteri perspektifi
Rune’un, topluluğun temposunda çalışan bir dijital deneyime ihtiyacı vardı: koşucular sıradaki antrenmanı hemen bulabilmeli, antrenörler ise ayrıntıyı kaybetmeden programın bütününü görebilmeliydi. MadeByCat bu ihtiyacı, kulübün hareket biçimiyle tutarlı, anlaşılır ve mobil öncelikli bir planlama deneyimine dönüştürdü.
— Rune Sport ekibi
Credits
Design and development partner: MadeByCat.