Back to selected work

Independent project / Sports analytics

DiamondScout

Making a busy baseball season easier to follow.

My scope
Product direction, frontend interfaces, and baseball API integration.
Built with
Next.js, React, TypeScript, Tailwind CSS
Status
Live independent project
DiamondScout dashboard with player search, navigation, and starting-pitcher cards beneath a baseball analytics introduction.
The dashboard brings navigation, player search, and today's starting pitchers into the first screen. View full size (opens in a new tab)

The problem

Following baseball means moving between today's games, season statistics, and longer-term player research. The interface needs to help someone find the right level of detail without losing their place in all that data.

My contribution

I build DiamondScout as an independent project, bringing together my interest in baseball and my React and TypeScript work. My scope covers the frontend experience and the integration of baseball data into player, prospect, and league views.

Inside the interface

DiamondScout league leaders showing season and hitting or pitching controls above aligned rankings for home runs, batting average, and runs batted in.
League leader panels use the same row structure across categories, with player identity on the left and the statistic on the right. View full size (opens in a new tab)

Give every number a consistent place.

Leader panels repeat a simple structure: rank, player, team, and value. Consistent alignment makes it easier to scan a category and move between categories. Player names lead directly to individual profiles.

Put the scope above the results.

Season and hitting or pitching controls sit above the leader panels. Keeping those choices close to the data helps someone understand which group of players and statistics they are looking at.

Keep player lookup close by.

Search lives in the main navigation, alongside direct routes to teams, leaders, and prospects. The interface also exposes keyboard shortcuts and search-navigation instructions for people who return frequently.

What I built

  • A live dashboard with starting pitchers, standings, and season leaders.
  • Reusable ranking panels connected to player profiles.
  • A React and TypeScript frontend that organizes multiple baseball data sources into connected views.

What I would evaluate next

The next thing I would measure is how quickly someone can move from a player name to the statistic they need. That would give me a concrete way to evaluate the search and navigation as the product grows.

Screenshots from the live product, captured September 11, 2026. Product screens and data may change.