I am in the same boat, I started a side project a few months ago and released the MVP without looking too much into the competition. But it turns out there is a lot of it. The reason I am not going to stop working on it is: - I am learning a lot while developing the new features(using lots of different tech that I don't necessarily use in my day job) - it allows me to channel some creativity that I did not know I had…
There are advantages because you can see what features work or not before you build them into your product.
Ask HN: Are you put off building something because it already exists?
31–40 of 301 posts
Re: Ask HN: Are you put off building something because it already exists?
#32- Perhaps the service isn't able to meet 100% of the user needs, maybe because some users jumped onto that product because it was the closest (but not perfect) solution to their problem. Or maybe the company grew too big and lost focus/decided to ignore the needs of a few because they moved up.
- What about the non-technical parts of the product/service? Sometimes you can differentiate by user experience (the note-taking app "Notion" is a really good example of this, and totally swept me up. Kudos to their team!).
Re: Ask HN: Are you put off building something because it already exists?
#33the problem I'm having is how do I enter a niche space and get customers away from my competition?
the niche I'm entering has existing solutions, but they're messy and difficult to use (based on early feedback). I want to simplify a lot of it, but I know in the beginning I'm going to lack a lot of features that current existing solutions have.
If I keep at it, I'm sure I'll get to them eventually, but I think the lack of some of these features could be a major deal breaker for some potential customers early on. I don't want to cater to just larger customers, but I don't want to ignore them either.
I'm just not sure what the right balance is going to be, but I think the only way I'm going to figure it out is by engaging with potential customers for their input, while also not pushing them to jump over unless they think we're ready.
Re: Ask HN: Are you put off building something because it already exists?
#34Re: Ask HN: Are you put off building something because it already exists?
#35Professionally, I'll write only the code that I feel comfortable that I understand and can maintain. Otherwise, I'll look to third party open source code. Unfortunately, I have been bitten a few times recently by popular and well-maintained but poorly designed or tested libraries that include frustrating bugs.
In my personal projects, I like to challenge myself. I will choose to write any and all code that isn't provided by the language's standard library even if trustworthy open source libraries exist that I would use in a professional situation. I like to think of it as "desert island programming". If nothing else, it has taught me interesting things about all sorts of domains I wouldn't have otherwise sought to learn about. And that knowledge is worth the struggle when making it to market as fast as possible isn't the goal.
There are other reasons for reinventing the wheel besides supplementing your personal understanding. Sometimes the licenses of the alternatives are inadequate. Of course, that's a somewhat personal assessment. Sometimes the alternatives are poorly maintained, poorly designed, or have fundamental flaws or bugs. Sometimes it's not that the existing software is bad per se. Oftentimes writing software involves trade-offs and perhaps the trade-offs the major library's authors have chosen are different from what you might choose. Recreating it yourself can clue you in to these trade-offs and gives you the opportunity to explore different paths.
Re: Ask HN: Are you put off building something because it already exists?
#36Just because something exists, doesn't mean it can't be done better, faster, smarter, cheaper. In fact it's usually a good sign that someone else built it first because it may indicate a valid market.
Re: Ask HN: Are you put off building something because it already exists?
#37A while ago, I was in the same boat. Why try to recreate GitHub, or Uber, or Salesforce, or Facebook? And once I discovered any competitors in my idea's field, I would chalk it down to "not worth trying" and call it a day. But then I realized, if my town can have 3-4 Chinese restaurants with the same exact menus (probably supplied by the same exact distributors), and they've all operated continuously for over a decad…
You're making a really good insight here. I just wanna give some examples to add to your point. Here in Indonesia there are 2 big Uber clone (at least initially): Gojek and Grab that are both unicorn. In the beginning, they both started off ride-hailing. But after about 4 years, Gojek morphed into a payment company like Chinese We-Pay. It seems they were thinking of ride-hailing as a good customer-acquisition strateg…
Re: Ask HN: Are you put off building something because it already exists?
#38You come up with a brilliant idea, you obsess over it, you Google some info, and on your screen lies your idea, being done by someone else, for the last two years. You’re all too familiar with that sinking feeling in your stomach that follows. You abandon the idea almost immediately after all that excitement and ideation.
First (as already mentioned), existing solutions prove your idea — their existence proves that you’re trying to solve a real problem that people might pay to have solved. And it proves that you’re heading in a direction that makes sense to others, too.
Second, and this is the biggie: The moment you see someone else’s solution, you mar and limit your ideas. It suddenly becomes a lot more difficult to think outside the box because before, you were exploring totally new territory. Your mind was pioneering in a frontier that had no paths. But now, you’ve seen someone else’s path. It becomes much harder to see any other potential paths. It becomes much harder to be freely creative.
Next time you come up with that great idea, don’t Google it for a week. Let your mind fester on the idea, allow it to grow like many branches from a trunk. Jot down all of the tangentially related but equally exciting ideas that inevitably follow. Allow your mind to take the idea far into new places. No, you won’t build 90% of them, but give yourself the time to enjoy exploring the idea totally.
When I do this, once I do Google for existing solutions, I usually find that all the other things I came up with in the ensuing week are far better than what’s already out there. I have more innovative ideas for where it could go next; I have a unique value proposition that the other folks haven’t figured out yet. But had I searched for them first, I never would have come up with those better ideas at all.
Finally, I’ll say this: if you see your idea has already been done and you no longer care about it, then it probably wasn’t something you were passionate enough about in the first place; it was just a neat idea to you.
Re: Ask HN: Are you put off building something because it already exists?
#39Depends on how your product will compete, but being first entrant isn't always good. Apple copied their PC from IBM, their tablet from Microsoft, and their ipod from others. They're successful because they do it better. Can you?
Re: Ask HN: Are you put off building something because it already exists?
#40I agonized over so many competitors, and none of them mattered. If you're going to do it, just do it.