A premium football tactical workspace for building, saving, and sharing formation lineups on an interactive pitch.
Summary
VRTX is an early-stage, full-stack football platform with a polished Next.js frontend and an Express backend split into separate workspaces. The current build ships a responsive football pitch with a formation-based lineup builder (7 formations, drag-and-drop player placement), with Firebase auth at the core and a protected API boundary between the client and the Express API. The long-term vision is a differentiated product that combines modern sports UX with coaching-level tactical depth.
Problem
Football fans, coaches, and analysts lack a fast, polished way to build and tweak tactical lineups and share them with others.Existing tactical editors feel clunky, dated, or bloated, with no premium, SaaS-grade experience designed around quick formation switching and visual player placement.A Next.js 16 App Router frontend (React 19, Tailwind CSS v4) driving an interactive, drag-and-drop pitch UI.An Express 5 (ESM) backend, kept in a separate workspace, exposing a protected API boundary gated by Firebase-verified auth.
Solution
A full-stack web app that puts an interactive football pitch at the center: users pick a formation, place players visually, and (on the roadmap) save, share, and revisit lineups. The architecture is built to scale cleanly from a lineup editor into a full tactical workspace with teams, player search, shareable links, and future real-time collaboration and AI insights.
Features
Architecture
Frontend
Backend
DevOps & Tooling
VRTX is a monorepo with two workspaces: /frontend (Next.js 16 App Router, React 19, Tailwind CSS v4) and /backend (Express 5, ESM).
Firebase handles authentication on the client, issuing credentials that gate access to the Express API.
A protected API boundary sits between the Next.js frontend and the Express backend so only authenticated requests reach sensitive routes.
The frontend is organized around a product-oriented structure — app, components, features, lib, services, and types — supporting the interactive pitch and formation logic.
Bun is used as the package manager and lockfile across both workspaces.
The planned data layer is Supabase + Prisma + PostgreSQL, with Vercel targeted for the frontend and Render for the API once deployed.
Results
5 commits
1 star
0 forks
0 open issues or pull requests
No live deployment yet — pre-release / portfolio-stage build