What happened to Tribely?
Let’s not complicate this. I thought about it a lot, and the reason was simple: the slope of my learning curve was getting close to zero. That made me realize I need to work on certain skills. Skills that would’ve made the whole process smoother and more efficient. The good part is now I know exactly what to work on.
Ideation: The idea itself could have been better. It’s hard to scale and grow a user base, especially with no money. The only reason someone would use Tribely is if people around them were already there. It wasn’t built for strong individual use cases. Looking back, a better idea could’ve been something like an app version of Sonic, plus the ability to see each other’s workout logs. The truth is, it wasn’t clear to me what I wanted from this. I never wrote down exactly what I wanted to build. I just jumped in, and that caused problems when ideas contradicted each other.
Lesson learned: have a specific end goal written on a paper.
Interest: I started losing interest, which isn’t the right reason to quit, but I still did. I was thinking long-term (could be wrong, but that’s life). At the time, I was really into machine learning, so I shifted focus there. These days, it’s algorithms and computer architecture (I’m trying not to fall into the rabbit hole). Funny enough, I got interested in algorithms because I realized how important they are while building Tribely. So that’s a win.
Do I regret quitting? As of Sept 2025, no. I learned a lot since then and built a clearer perspective and better goals.
Anyway, you can still try Tribely here (I’m not working on it anytime soon, maybe never):