← Back to selected workProduction full-stack workPlatform closed · Case study
Footy Greece
Making everyday workflows more reliable for coaches, athletes, parents and academy staff.
Full-stack developer · Production maintenance and feature deliveryReact 19 / TypeScript / ASP.NET Core / SignalR / SQL
The contextFooty Greece was a sports platform built as a multi-application React and .NET ecosystem. I worked remotely on production features and issue investigation from December 2025 to September 2026. The platform has since closed.
This case study summarizes completed work items assigned to me and my CV. The product is no longer available publicly.
How it connects
The workflow.
- 01User workflow
- 02React interface
- 03ASP.NET Core API
- 04SQL data
The application layers I worked across. This is a workflow overview, rather than a screenshot of the retired product.
Engineering details
Inside the work.
01A complete registration journey
Worked on replacing side-panel registration with a dedicated page, consistent login/registration navigation, inline validation and mobile-friendly layout. This brought account creation into the same visual and interaction patterns as the rest of the application.
02Role-aware conversations
Resolved chat issues involving conversation-name editing permissions and the availability of other coaches as recipients. These tasks required the interface to reflect who could perform an action and which users belonged in a conversation.
03Consistent athlete information
Addressed evaluation values that differed between summary charts and profile views, alongside attendance-list reporting. The goal was to make the same underlying information understandable and consistent wherever it appeared.
04Clearer payments and direct course navigation
Worked on grouping future payments separately in parent views, and taking learners directly to the course they selected. Both changes reduced ambiguity in everyday product use.
What I took from it.
- A small UI issue can originate in routing, permissions or the data returned by an API.
- Consistency across screens matters as much as the correctness of an individual component.
- Production maintenance means tracing an issue through the interface, API and data layers.