FitLog.
A fitness tracking application built with Clean Architecture, separating concerns across layers for long-term maintainability and scalable feature growth.
Highlights
- Layered architecture with clear domain boundaries
- TypeScript frontend paired with C# backend
- Designed for maintainability and future feature expansion
- MIT licensed open-source project
PROBLEM
Most fitness apps start with a few screens and grow organically. Over time, workout logic ends up inside UI components, database queries leak into controllers, and every new feature becomes harder to ship. The cost is rarely visible on day one, it compounds as the product scales, onboarding slows down, and regressions multiply.
SOLUTION
I structured FitLog around Clean Architecture with explicit boundaries: a domain layer that owns business rules, application services that orchestrate use cases, infrastructure for persistence and external APIs, and a TypeScript presentation layer. The C#/.NET backend exposes a stable API surface while the frontend focuses on experience, so each layer can evolve independently without breaking the whole system.
Results
- Domain, application, infrastructure, and presentation layers with clear ownership
- New tracking features (meals, workouts, progress) without rewriting existing modules
- Testable business logic isolated from frameworks and UI concerns
- Open-source reference for enterprise-grade layering in a real product context