rajatkulk
Joined 6 years ago
Joined 6 years ago
As for revenue, it did give me enough confidence to quit my day job (was pretty well paid for my country), and Octarine since the past 3 months, has exceeded that as well :)
Also the app's been around for over 3 years now, and isn't vibe coded (since I saw it in this thread around vibe coding apps).
Open to any feedback if you've been using it for a while
Haven't checked the repo, but guessing you using the opendota apis? Anything that you do different compared to dotabuff/opendota?
In the counter pick, would love if you could enter a match ID to prefill data, and then see what could've been a better pick? Last picked Ember but was countered by the enemy picking Ursa on their last pick. Given the rest of the draft would a different hero would be better?
Built with tauri & rust, and is more performant, and doesn't rely on random contributions for basic things as plugins.
Disclaimer - I build it.
Having to rely on random devs for the most basic functionality and passing it off as `community does what it wants` is weird. Either add it in yourselves, or accept the fact that given your app requires external contributors to work at a little above the basic level, there are going to be security issues.
Writing a whole blog post, and throwing shade on "other apps" that have far more dependencies than Obsidian is weird to me.
Anyway, it seems like you can't really talk bad about them, since there's a huge following that just comes at you, and that feels weird, cause they apparently can throw shade, others can't just talk back.
I try to solve this by running a small embedding model on device, and the Ask Octarine feature, suggests what you may need to find/look. Isn't as sophisticated as Spotify's or the recommendation algo, however it provides a nice starting point, and then allows you to chat/RAG your way around notes!
Here's a small documentation writeup & video about it, if you want to look instead of try - https://docs.octarine.app/working-with-ai/ask-octarine
If an fps counter makes an app seem illegitimate to you, and the countless changelog, user testimonials don’t help, then nothing I say will convince you otherwise, so I’m not going to waste either of our times :)
The use case is far too niche to move engineering efforts to immediately, so it'll be prioritised when either:
- the ask quantity increases.
- when an adjacent part of the code is being improved/fixed and this could be tacked upon in the same release.
Thanks for the suggestion!
I don't do marketing (I do a post on reddit once in 3 months or so for updates, but it doesn't get that much traction). Feel like it's word of mouth. Some of the early users told more people they knew, and they did the same.
Now a ton of customers bring the name up in their reddit threads (like you did here), and that's generally it.
I'd love for conversions to be higher compared to the install count, but it's still healthy for an indie project with a relatively higher price point (people are too used to free, or $19 products).