TypeScript · Next.js · Data visualisation & AI integration
SportSee Sports data you can really explore.
A TypeScript and Next.js application connecting sports data, Recharts charts and an API-connected AI coach. Dashboard, conversation and programme generation in one interface.
An embedded version built from the application’s code, with no account to create. Explore the dashboard, profile and planner using fictional data. The coach and planner use predefined examples. No AI model is called.
BEHIND THE PROJECT
How do you turn activity data into a useful dashboard?
A dashboard for exploring activity data and comparing periods in a few interactions.
01
UNDERSTAND
The starting point.
A list of sessions and measurements makes trends difficult to spot, particularly on a small screen.
02
DESIGN & BUILD
The project in practice.
Frontend development in TypeScript with Next.js and React, using Recharts charts, TanStack Query for data and server routes to communicate with the API. Integration of the AI coaching journey and training programme requests through to calendar export.
TypeScript
Next.js
React
Recharts
TanStack Query
API REST
LLM integration
ICS export
01The need
02The solution
03Everyday use
Project scope.
TypeScript/Next.js development, Recharts visualisation, data API integration and connection of the user journey to an AI coach.
A typed interface connected to data
TypeScript describes profiles, sessions, coach responses and programmes. TanStack Query manages requests and their state. Next.js server routes relay API calls with the user session.
Charts you can interact with
Recharts displays distances, heart rate and goals in React components adapted to the available space. Changing the period lets users explore sessions without leaving the dashboard.
An LLM integrated into the user journey
The frontend sends the question and conversation history to the AI coaching service through an API. A second flow sends a goal and date to request a programme, then offers an ICS calendar export. Loading states and errors are handled in the interface.
03
WHAT CHANGES
Data that is easier to read and compare.
Weekly navigation and readable values make it possible to explore activity. The preview uses fictional data.
Yes, if the API exposes the required data and authorises access. The frontend must handle authentication, loading, errors and units, then present information in views suited to its users.
02
How do you make a chart usable on mobile and with a keyboard?
+
Interactions must work without hovering, with sufficiently large controls and text-readable values. In this embedded application, buttons change the period and charts retain their interactions. Displayed data is fictional.