xPitch

The description states that xPitch:

• Processes .fit files from smartwatches worn during football matches.
• Generates insights such as positional heatmaps, zone occupancy, movement trails, distance covered, sprints, HR zones, and role estimates.
• Uses a browser-based .fit decoder with no upload required for initial analysis.
• Allows users to save matches to the cloud (via Supabase), share via public link, or export images for social media.
• Includes semi-automatic session splitting based on heart rate data.
• Estimates pitch orientation using either user input or PCA-based methods.

It is described as a tool that turns raw GPS and HR data into football-specific visualizations and reports — with an emphasis on privacy (local processing) and ease of use (no upload needed for core analysis).

Inference The product appears to be a lightweight, single-user analytics platform built around the idea of making personal football performance data accessible in a way similar to how Strava presents running data.

The description states that xPitch is:

• “Strava for football player”
• Designed to analyze football matches like professional breakdowns on TV — heatmaps, positional zones, sprint counts, heart-rate load.
• Built around how football actually works (stop-start, multi-directional, played in halves).
• Aims to provide a “football-specific” experience that Strava lacks.

The author also notes:

• The tool was built with AI assistance (Codex), which accelerated development.
• It started as a prototype and evolved into a full product loop.
• It works for personal use and has been tested by friends, who requested accounts.

Inference Positioning is centered on offering a niche, privacy-focused analytics solution for amateur football players. The claim of being “Strava for football” suggests an intent to capture a segment of the market that lacks dedicated tools — but no evidence exists of actual adoption or competitive positioning beyond self-reporting.

The description states:

• xPitch is aimed at football players who want to analyze their own performance using smartwatch data.
• It targets those who play regularly and care about metrics like distance, sprints, HR zones, and role estimation.
• Friends have asked for accounts, suggesting early interest from a small group of users.

Inference The ICP appears to be amateur or semi-professional football players with access to smartwatches and .fit files. No evidence exists of segmentation beyond this, nor any indication of whether the tool targets coaches, teams, or clubs.

The description states:

• Matches can be saved to the cloud using Supabase.
• Users can share matches via public links or export images for social media.
• The author mentions a future goal to open it up to everyone — implying a potential freemium or open-access model.
• No pricing information, monetization strategy, or revenue streams are mentioned.

Inference There is no clear business model evidenced. The tool seems to be free to use for personal purposes, with possible future monetization through cloud features or expanded integrations. The lack of any pricing or commercial structure makes it difficult to assess scalability or sustainability.

The description states:

• Built using canvas, GitHub, OpenLayers, PostgreSQL, Supabase, TypeScript, Vite, Vue.
• Uses a local-first .fit parser that decodes binary data entirely in the browser.
• Implements custom logic for pitch geometry and orientation estimation (PCA).
• Includes semi-automatic session splitting based on HR signal.
• Deployed on GitHub Pages with no paid infrastructure.
• Developed using AI tools like Codex to accelerate development.

Inference The technical stack is lightweight, modern, and focused on client-side processing. The use of AI for rapid prototyping and refactoring suggests a lean engineering approach. However, there is no evidence of scalability, performance testing, or production-grade infrastructure beyond GitHub Pages.

The description states:

• The founder has been using the tool to track his own matches.
• Friends have asked for accounts.
• A small amount of historical data exists (from two matches).
• The author notes that he doesn’t yet have enough data for meaningful analysis — “unfortunately, I only play twice since I build this project.”

Inference There is minimal traction or user adoption evidenced. The tool appears to be in early stages of development and personal use only. No metrics on active users, retention, or engagement are provided.

The description states:

• xPitch aims to fill a gap left by Strava, which treats football like a jog.
• It is positioned as a more accurate analytics tool for football players.
• No mention of direct competitors or market analysis.

Inference There is no evidence of competitive landscape analysis. The author does not name other tools or platforms in the space, nor does he describe how xPitch differentiates from them. This leaves open whether such a niche exists or if there are existing solutions already addressing this need.

• No user data or adoption metrics: The tool is described as personal use only with no evidence of broader traction.
• Single-person development: Only one developer (the founder) is involved, raising questions about scalability and long-term maintenance.
• Limited data sources: Relies solely on .fit files from smartwatches; lacks camera or ball tracking data.
• Unproven commercial viability: No pricing model, monetization strategy, or revenue path described.
• No third-party validation: The tool is self-reported with no external verification of performance or accuracy.

Inference The project is in a very early stage and lacks any signs of market traction or business maturity. It may be a proof-of-concept rather than a scalable product.

1. What percentage of your time was spent on AI-assisted development versus traditional coding?
2. How many users have you personally tested the tool with, and what feedback did they give?
3. Are there any plans to integrate with specific smartwatch brands or platforms (e.g., Garmin)?
4. Has the tool been tested under various match conditions (e.g., different pitches, weather, formats)?
5. What is your long-term vision for monetization or product expansion?
6. How do you plan to scale beyond a single developer?