I am a Product Manager based in Silicon Valley, USA. I have an idea that I would like to develop as a product. I am technical enough in a sense of knowing the tech side of what I want to build, how I want to build it, etc, but I am not a developer. What I am thinking of doing is to create a customized software solution across all 3 mobile platforms, iOS, Blackberry, and Android.<p>I would like to outsource my product development to an IT firm or developers/hackers. There is a big chance/possibility that these firm/developers are outside USA based because of the potential cost as I am investing my own capital (I am looking for local developers or within USA as well).<p>Now the question is how vulnerable am I if I outsource my development completely. Vulnerable means if my source code is stolen or the firm/developers instead develop their own product based on my idea. Of course I would have them sign an NDA and non compete document and all that, and most of the time I would think I am protected if the firm/developers are USA based, but how about if it's non USA based (most probably India, Russia, or some eastern europe based).<p>Am I completely screwed if these things happen (even if the developers/firms have signed all NDAs, non compete, and so forth)? Would I be able to file a lawsuit on the developers country and maybe USA? Do NDAs and non compete agreement they sign are even applicable in their residence country? What options do I have if these happen to me?<p>Thank you for the advise.
Filing a lawsuit in a foreign nation costs six figures and up up up, exposes you to the substantial risk of losing due to home court advantage, and gives you the upside that the fly-by-night developer who stole your idea gets told in a very stern tone of voice to please not do it again. It is not a realistic way for you to cover the downside risk of getting your code stolen.<p>Want good news? Your idea is worthless, so it is no biggie if it gets stolen. The source code produced is likely to be overvalued at "worthless", so if one of your competitors gets a hold of it, you'll quickly be ahead of the game as long as you don't do anything excessively stupid like attempting to use that source code yourself. (You may succeed in getting code with actual value if you're really good at both picking your provider and managing the outsourcing project, which is <i>ahem</i> not a cheap, easy, do-in-your-spare-time endeavor.) No company worth building is at risk of getting knocked off by a cheap outsourcing company -- if all it took was enough monkeys banging on typewriters to make a software company, they'd already be doing it.<p>My bona fides: managed outsourcing operations for a few teams of a Japanese multinational for a few years.
Personally, I would look for a US based developer that would do it for the amount you have to spend + some equity. You would be surprised how many talented individuals you will attract when they know that you have some skin in the game, the big problem that technical-cofounders have is not that they think every idea is stupid but that they perceive you as just another "I have and idea" guy, when you have some money in they game, they know you are serious and will listen to you. To be honest if you have to worry about money enough to outsource, you probably don't have enough to outsource right and therefore your risk of failure is even higher than a local or at least US based candidate. Adding time zone, cultural and language barriers to the fact that you have no outsourced software development experience is a recipe for disaster. Also I don't mean to be harsh, but if you think yours will be different, it won't the odds are stacked against you and for every one that succeeds there are at least 20 that fail and end up costing 3X the cost that it would have originally cost to have it built with variables that you can manage. Outsourcing takes more management oversight, it is an economies of scale thing, at a certain point a project gets big enough that it is cheaper to hire managers to manage less expensive developers overseas. But just because that recipe works for large projects does not mean that it scales down well. Hiring a manager to manage 1 or 2 overseas developers pretty much negates any cost savings that you would have gained.
You have to be careful which countries can enforce U.S. based NDAs. You will probably need to translate it to a native language and have it notarized by a native lawyer and signed by the individuals (not by the company since that might not work in some cases). This might get expensive.<p>To kitcar: From what I've saw on the Internet, Eastern Europe has very good developers/hackers if not the best. Probably, I'm just biased here.
> I could have tell Apple, Blackberry, and Google to stop the app listing, but that's a long process and during the process, money are going to the developer ways.<p>If this is a key point of worry, get the ball rolling for your registered trademark for the <i>exact</i> name that you will appear in the app stores, and confirm that name isn't already taken in the stores, and ideally you can get that name .com/twitterID/facebookID to own your brand.<p>You can use registered trademark to deny others the app listing by way of your registered trademark status, its straightforward for Apple/Google/Microsoft/et. al. to make a call on app store removal based on trademark infringement.<p>Regarding development, I've done the same with a startup as you are thinking of with a similar product background, it can be done but the challenges are maybe not what you expect - code theft is not a top concern if you screen correctly. Send me an email, or we can grab a coffee sometime, I'm also in Silicon Valley.
Most outsourced developers are pure rubbish.
I cringe when I have to open a project that was outsourced.<p>At the small level it's fine, but when building larger apps there are just too many barriers to make it efficient.<p>Including developer programming and communication skills.
Depends on what country you send the work to, and if there is rule of law in that country. Also depends on the amount of money on the line.<p>If its a big concern, and your project allows it, split the project up into separate modules, each worked on by a separate team - at least that way no single team would have full access to your codebase. The code quality could potentially suffer though, as there would be little consistency in style (unless you establish guidelines and enforce them)
I think having them steal the work is the least of your worries, you have to first actually get them to produce a successful product across three platforms. This is something thats challenging to do in-house so good luck making that work when dealing with non-native English speakers working on a different-time zone