AllGameTimes (Blazor)
The .NET Blazor original — schedules and matchup analysis across five leagues in one place, and the app whose performance problems justified a ground-up Rust rewrite.
What it is
Following more than one sport means more than one site, more than one layout, and more than one set of habits to relearn. AllGameTimes puts them in one place: pick your league, see the schedule, and drill into a game.
It covers the NFL, MLB, and NBA alongside NCAA football and basketball, plus soccer — spanning both professional and college in the same interface.
Built with Blazor
This is a .NET Blazor application, which means the UI is written in C# rather than JavaScript. Razor components give each part of the app — the layout, the navigation, the side panels, and each league's pages — a clean, strongly-typed boundary.
I chose Blazor deliberately here: for a data-heavy, server-driven application where most of the work is fetching and shaping results, keeping one language across the stack removes an entire class of JavaScript-to-C# type mismatch bugs.
Structure
The application is organized so each league owns its pages while sharing a common shell:
| Area | Contents |
|---|---|
| Layout | The main layout, navigation menu, and reusable side panels — including an NFL-specific panel variant. |
| League pages | Dedicated pages for NFL, MLB, NBA, NCAA football, and NCAA basketball, each with its own stylesheet so a league's presentation can diverge where it should. |
| Schedules | A separate schedules area per league — CFB, MLB, NCAAB, NFL, and soccer — because "what's on today" and "what's the full season" are genuinely different views. |
| Matchup views | Dedicated matchup components and modals per league, so a head-to-head comparison can show league-appropriate stats. |
| Info pages | About, contact, privacy, and error pages. |
One app, two restaurants, one nearly-table-less UI
If the structure above looks like a hybrid of a restaurant site and a sports site, that's because it genuinely is. The shared shell, side-panel pattern, and info-page structure came from a restaurant application I'd built previously, and AllGameTimes repurposed that foundation for league-based content instead of menu-based content.
Reusing the shell saved real time — navigation, layout, and the modal pattern were already solved. But the shared visual style still shows through in places where a sports site would want something different. It's a fair illustration of both the benefit and the cost of starting from an existing codebase.
Assets and leagues
Each league gets proper visual treatment — dedicated SVG icons (NFL, MLB, NBA, NCAA football, NCAA basketball, baseball, soccer) plus per-league landing images, so switching leagues feels like switching products rather than changing a filter.
Hosting
Deployed on Railway with PostgreSQL backing the data and Redis available for caching — the arrangement a schedule-driven app needs when the same queries run for everyone at the same time of day.
Why it was rewritten
This version was slow, and the slowness turned out to be bugs rather than limits. The database query behind the worst page always ran in 37 ms; the other 7.6 seconds were redundant upstream fetching and HTML assembly. The /soccer page shipped 1.4 MB of payload and took 7.6 seconds to render.
Rather than patch around it, the app was rebuilt from the ground up in Rust — same sports, same data, a completely different shape. The rewrite is AllGameTimes (Rust), and it serves the same soccer page in 2 KB and 10 ms.
This page stays because the before-and-after is the useful part. The rewrite's README documents the five root-cause bugs and the benchmark evidence behind every phase gate.