I've been working on an app that I believe will be beneficial to millions of people. And I've seen a few built and deployed that are SOOOOO close -- and even an announcement by a VERY big player that is also close.
But frankly, I believe they've all misfired.
And that it's my app that will literally change the world.
So I keep plugging away.
Alone.
We'll see if anybody actually uses it though. It's always a crapshoot.
I already dropped the ball once when I had essentially the same idea as Lyft or Uber -- but decided not to pursue it when I read Apple's rules against transportation-related apps.
I'd be willing to bet that hundreds of us had that idea. It was that obvious.
But Uber and Lyft actually built and deployed something.
And apparently those rules were rules that could be broken.
Oh well, live and learn.
Best of luck not dropping the ball this time!
It would be interesting if someone could dig up the old apple App Store Review Guidelines from whenever Core Location first became available.
Currently it disallows "Apps that use location-based APIs for automatic or autonomous control of vehicles, aircraft, or other devices will be rejected".
But I'm fairly certain that at the time it disallowed transportation industry related apps, and specifically mentioned trucking and taxis.
Which was irritating to me because during the dot-bomb at the turn of the century I had been reduced to the role of taxi driver for a time.
And the only way to actually get any fares through dispatch was to bribe everybody and especially the radio guys. I hated it and really had to work hard to make money from people hailing me.
So when I first learned of Core Location, my first thought was "motherfuck taxi dispatch - I can make them irrelevant with iPhones now".
Seriously, I'd love for someone to dredge up the old version of that document so I can read over it again.
--------
0) It's validation.
1) Execution will be different, they might bork it or serve different customer segments.
Cons
--------
0) Find/create durable competitive advantage/s
1) Win-Lose/Lose-Lose competition sucks because it's often dumb (see also: Peter Thiel)
Is like food stores cluster in a location, is easier if exist a way for the customers to see "look, here is where food can be buy!"...
---- Also:
Not only somebody else is building it, many must already do it... is very unlikely somebody truly open a "new market".
---
The same book say you must be the #1 in a market. Failing that (like the 99% case) you must create a niche that make you the #1.
For example:
You can't be the #1 beer seller
But,
You can be the #1 beer with fruit flavors seller.
---
I before stop to do like a dozen of projects, scared by MS, Google, and others when them announce some stuff (that sometimes, only vaguely :( ) were similar to my ideas.
Now? I regret all that! None of the stuff they do was even closer to the style I was looking for...
Now, I lost my opportunity to do fun/side projects (now, need to bring money to the table). I'm trying to build 2 side projects, and despite are "common" and I move slooowwwww (responsibilities!) I don't worry anymore: Is more likely I will fail because myself, and even if I build a "copy-cat" is clear that I will bring something else to the table, just because I'm not the others...
So, don't stop ever because what are others doing.
If it's open-source, see where you can contribute, for example, documenting the code or adding a feature you think they're missing.
If it's not open-source, see if they're hiring. In your cover letter mention that you had a similar idea, but it differed in x, y, and z ways, and include the pros and cons of your your different features and implementation methods.
But I always note I don't actually decide what goes into that software. I can argue about why X feature is needed or why Y should be implemented in Z way, but I don't own that repo. Of course this is the beauty of open source just fork it (with the cavaet of watch the license which many probably doesn't care or doesn't have the knowledge to understand what X license mean to a user and to a contributor). But if I were to test my own ability and feel proud "yes I build it from scratch" I will build one from scratch. There is just that one idea that "I wish I was famous and getting tons of likes and respects because I built something that hundreds of developers are benefiting, being original creator vs a contributor.
If you think you can build something of value for people and you care about the problem then do it or join others already doing it. If a competitor makes a mistake, learn, and if they succeed, adapt. Everything else is a distraction from solving actual problems.
There's many ways to differentiate. Maybe yours can be more featureful. Maybe it can be simpler; not everyone wants everything to be covered in options. Maybe you can iterate faster; maybe you can offer more stability and a more "corporate-aligned" update schedule.
Look for people who don't like the other person's product, find out why, learn from their mistakes, and try to serve users that they ignore.
[0] https://news.ycombinator.com/item?id=9663904 [1] https://news.ycombinator.com/item?id=9663203
Otherwise quit second guessing yourself and get back to work.
Any market worth being in, will have plenty of competition early on.
Primarily you have to ask yourself if you can add value to the segment you're talking about. If you have something worth-while to offer customers / users. Such questions remain regardless of the competition or lack thereof. If you've got something valuable to offer, build it. There is always an angle to take against a seemingly superior competitor, whether that's on price, features, support, customization, ease of use, et al.
It's all about the execution. If two people have a great idea the winner will be the one who executed better.
i.e. They scaled better, they used appropriate tools, they had a functioning team, they moved first, they listened to customers, they pivoted and stayed agile, they remained focussed on their goal etc. etc.
On the other hand, some products have network effect, which can make them hard to assail once they've got momentum.
Also don't forget the 10x 'rule' - you need to be 10x better than an existing product if you're doing the same as an established product.
As others have mentioned you may also be attacking different market segments e.g. business/consumer, geographical region, age group, etc.
Come to think of it, aren't there one or two books on the subject ;-)
If you want to build it, build it anyway. Build it for passion, for the experience, for interest, or for any other reason. Or don't, that is ok too.
We wrote two blog posts that you might find useful if you're in this kind of situation:
1. Why you should share your “secret” startup idea with anyone who will listen:
http://www.kilometer.io/blog/why-you-should-share-your-secre...
2. Don’t build anything until you have a clear startup mission
http://www.kilometer.io/blog/dont-build-anything-until-you-h...
If it is to learn something, the answer is obvious: build it anyway. You will still learn pretty much all of the things you otherwise would have.
If it is because you feel that the world needs this thing to exist, and it'll become a better place because it does: see if you can contribute to the other people's work. If not, see if what they're doing meets that need and be happy that other people shared your vision of a problem to be solved.
If it's because you wanted to make a company and earn a living: keep going. There are thousands of niches in businesses. You can find yours.
First, it will vet out the market of the product. We are told to look for something new and innovative, but truth be told, the best way to predict the success of a product is to analyze the performance of similar product.
Second, it will give you some insights on areas within your own product to improve as well as ideas on how to differentiate.
But, it ofcourse depends on what your building, the info i miss in de main question asked.
Execution is everything is a meme in part because execution reveals hidden assumptions we did not know we had. Two people who nominally set out to do the same thing, are probably not actually doing the SAME thing. Just like there are millions of different cars that can all be called "cars" and yet have many differences, projects can nominally be the same thing and yet not really.
- Product personality (aka voice)
- Initial Target Market's propensity to be enthusiastic about your product
- And much more.
Do your analysis of the market, and iterate based on customer feedback. Your idea might seem similar, but it might be completely different. The race is not to build your idea, the race is to find out if the idea is worth it or not.
Rarely is the market so small only a few can survive, and if it is that small, you are thinking too small. Markets worth going after can support multiple companies.
The first mover has to work really, really hard to get ahead and stay there.
So my response is, "So what". Build it anyway.
Figure out how to make the same thing more general purpose, more specific purpose, or different specific purpose.
Just make sure your version is different enough to avoid the trap of people using the other version because it's "good enough".
Or find a way to collaborate with them.
You know how there's only one personal computer platform because the other guys all gave up? Oh right, there's a bunch! Because different things can fill different niches, your take on the problem might fill some slightly different, but large demographic.
Build your version, less better, and then just kick their ass in business.
Apple was eaten alive by shitty IBM clones in the PC wars. SGI and Sun were decimated by commodity hardware. Linux destroyed a lot of high-end OSs and platforms.
You don't have to be better to do better.
Then again I only program as a hobby and everything I make is open so I have no financial motive to compete.
Would you answer the same?
You could even advertise yourself as being like your competitor, but the local option. Sell them on the idea that by paying you instead of the competitor, the money would stay in the community instead of going to the USA.
For example, I'm working in a little niche with some US competitors. But my partners have found that being "Made in Canada" is actually helping us sell to our local Canadian small businesses. Additionally, we're going to do a French Canadian version of our app and market in Quebec -- our US competitors haven't touched multiple language support. These small differentiators will help make us a successful business; not a Google or an Apple, but, a source of revenue that we built by ourselves out of nothing.
Competition is a sign that you're on the same track others have identified as being viable. It's much better to have competition than to be all alone.