Sumenia
Understand your training. Know what comes next!
I started building Sumenia because I was frustrated by something that probably sounds familiar to a lot of athletes:
We collect an incredible amount of training data, but actually understanding it still requires jumping between different apps.
One records the activity. Another handles routes. Another makes it social. Another gives you training metrics. And after all of that, you're still the one trying to connect the dots.
So I started building what I wanted to use myself.
Sumenia.
The original idea was relatively simple: bring training data together and make it understandable.
It didn't stay simple for very long.
Sumenia now combines activity recording, route planning, training and fitness analysis, health and recovery context, community features, training planning, an Athlete Timeline, 3D visualizations, an Academy, and Sumi — an AI layer designed to understand an athlete's own data and confirmed context.
But the part that may be more interesting to Indie Hackers is how I'm building it.
I'm a solo founder. There are no employees.
I'm using AI-assisted development extensively, but not by asking AI to randomly generate an app. I define the product logic, architecture, UX, calculations, privacy boundaries and decisions, while AI helps me execute, test, challenge and iterate much faster than I could traditionally.
That has allowed me to build at a scope I wouldn't have considered realistic for one person before.
It has also created a completely different problem:
When you can build very quickly, deciding what NOT to build becomes incredibly important.
I'm now spending a lot of time on exactly that — reducing friction, testing first-user journeys, validating reliability, simplifying the product and making sure the breadth doesn't become complexity for the athlete.
Privacy is another hard constraint. Training and especially health data are personal, so “add AI” can't simply mean sending everything everywhere. I'm trying to make privacy part of the product architecture rather than something added later in a settings page.
Sumenia isn't publicly launched yet, but the product and live demo are already online:
I'd genuinely value criticism from other builders.
If you were building this, what would worry you most: the scope, positioning, onboarding, AI, or something else entirely?
And if you try the demo and something is confusing, I'd rather hear that now than from users after launch.
Comment